Hi All,
I have few questions regarding Database mirroring.
I am just comparing log shipping and database mirroring. In log shipping, everything is handled via sql agent jobs i.e. "LS_" jobs which takes backup, copy backup and restore it on secondary server. This is what happens in case of log shipping.
On the other hand, in Database Mirroring, the log records or log stream is sent to the Mirror server and thus maintaining a hot standby database for Principal database.
I have below questions regarding database mirroring.
1) Who is responsible for moving those transaction log records from Principal database to mirror database? I mean, who or which thread is going to read those log records on Principal and move to Mirror database ? I just know the fact that communication happens via endpoints but who is responsible for reading and transferring those log records to the partner server?
2) Secondly, why can't I have the database which is participating in database mirroring as SIMPLE recovery model? In Log shipping we take transaction log backups and there is a reason of why we need to put the database in FULL recovery model but if I consider DB mirroring, sql server is reading the transaction log directly and if that is the case why can't I just have database in SIMPLE recovery model? Why should I need the database to be in Full recovery model for database mirroring?
3) Thirdly, on the Mirror side, which thread / who is responsible for constant replaying those log records/changes to the Mirrored database? In log shipping I know for the fact, constant restore of log backups does the replay on the Secondary server but in case of database mirroring , who does this ?
4) Finally, can I have a different database name for my Mirror database? Are there any known implications doing so?
Thanks in Advance.