Database Mirroring Best Practices and Performance Considerations
Maximizing the availability of databases is on the top priority list for many database administrators worldwide. Database mirroring is a new feature in SQL Server 2005 that can help minimize planned and unplanned downtime, thereby maximizing the availability of the database. Database mirroring transports the changes in the production database to a mirror database, either synchronously or asynchronously. The mirror database can reside either in the same data center to provide a high-availability solution, or in a remote data center to provide a disaster-recovery solution. Business requirements such as service-level agreements and performance, as well as technical factors such as log generation rate, network throughput, and I/O throughput, influence the deployment of database mirroring. This paper discusses best practices and performance considerations for implementing database mirroring.
Source: Microsoft SQL Server Best Practices
Database Mirroring and Log Shipping Working Together
Log shipping and database mirroring can work together to provide solutions for high availability and disaster recovery. You can convert an existing log shipping configuration to a database mirroring configuration. Although Microsoft only supports a single mirror database, you can set up log shipping from a database mirroring pair to additional servers, to provide multiple failover sites. Moreover, you can easily switch which pair of instances is using database mirroring and which instances are configured with log shipping.
Source: Microsoft SQL Server Best Practices January 2008
Download file & Read the full article:
-
Archives
- July 2008 (1)
- June 2008 (2)
- May 2008 (4)
- April 2008 (3)
- January 2008 (29)
-
Categories
-
RSS
Entries RSS
Comments RSS
