It’s been quite some time that I blog, Sorry about that I was busy with my movement from USA to India and changed my job part of life ,okay back to India (Pune).
Lastly I wrote a blog on High Availability techniques here and How to setup simple Mirroring Here. Continue on that following are some of the common difference of log shipping and Mirroring, actually both uses log and move the transaction “Mirroring used to call Real time Log shipping”. but the way it works makes it difference.
|
Mirroring |
Log Shipping |
| Principle can have single mirror | Multiple stand by servers can be possible. |
| generally good to have 10 DB’s for one server | No limit |
| No data loss and can be used as high availability like Clustering | May be some data loss as per schedule. And secondary server takes some manual work and time to be primary |
| Read log read and transfer the committed transaction through endpoints. | Transfer the log back up and restored at standby server. |
| only committed transaction | Committed as well as uncommitted and whole log backup restores. |
| PAGE repair is possible if principle database page gets corrupt | N/A |
| Mirrored DB can only be accessed using snapshot DB | Secondary server can be reporting server (read-only) |
| Principle and Mirror server should have same edition | Primary and secondary server should be compatible server for restore. |
| Require FULL recovery model | Require FULL or Bulk-Logged recovery model |
| requires Sql Server 2005 SP1 or higher – Enterprise or Developer Editions | Enterprise edition for Sql Server 2000 and even Standard edition for 2005 can works |
| Immediate data moved depending on SEND and WAIT queue | Can control the flow of data by scheduling jobs |
| As Immediate data moves, user error reflects at mirrored DB | As delay in data transfer can avoided user error. |
Hope this will help someone.
Thanx.
Vinay
