Effective Usage of SQL Server 2005 Database Mirroring
1. Effective Usage of SQL Server 2005 Database Mirroring by Satya Shyam K Jayanty SQL Server MVP www.sqlserver-qa.net [email_address] Lalandia, Denmark - March 09 th 2007
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
Notas del editor
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
Transaction safety is a mirroring-specific database property that determines whether a database mirroring session operates synchronously or asynchronously. There are two safety levels: FULL and OFF. SAFETY FULL Full transaction safety causes the session to operate synchronously in high-safety mode. If a witness is present, a session supports automatic failover. When you establish a session using ALTER DATABASE statements, the session begins with the SAFETY property set to FULL; that is, the session begins in high-safety mode. After the session begins, you can add a witness. SAFETY OFF Turning off transaction safety causes the session to operate asynchronously, in high-performance mode. If the SAFETY property is set to OFF, the WITNESS property should also be set to OFF (the default). For information about the impact of the witness in high-performance mode, see "The State of the Witness," later in this topic. For more information about running with transaction safety turned off, see Asynchronous Database Mirroring (High-Performance Mode) . Transport security in SQL Server 2005 involves authentication and, optionally, encryption of messages exchanged between the databases. In some situations, such as when server instances are not in trusted domains or when SQL Server is running as a local service, Windows Authentication is unavailable. In such cases, instead of user credentials, certificates are required to authenticate connection requests. The mirroring endpoint of each server instance must be configured with its own locally created certificate. 09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
In learning how to setup and configure Database Mirroring, there are many new and important concepts to master. If possible, you may want to follow a very specific process to setting up and learning Database Mirroring. It is recommended that you first learn the High Performance configuration and then move to the High Protection configuration. Then, if desired, you can move to the High Availability configuration. Starting with High Performance allows you to test mirroring with the least impact to your production environment. The High Performance configuration allows you to setup a Mirror database that has very little latency behind your Principal database, effectively setting up a form of real-time log shipping. Once you feel comfortable with the setup and configuration of Database Mirroring in the asynchronous form, you can then move to a synchronous form. Moving to a synchronous form will allow you to test the actual performance impact of Database Mirroring in your environment. There are many factors which impact performance: network speed and distance, speed of the mirror database/server, and transaction load. By moving to the synchronous High Protection configuration next, you can test the impact to performance without the possibility of an automated (and possibly unexpected) failover. Once the performance is deemed acceptable and you determine that automatic detection/failover is desired, you can add the required witness to the High Protection configuration to convert to the High Availability configuration. 09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
Effective Usage of SQL Server 2005 Database Mirroring 09th March 2007, SQL Server Open World www.sqlserver-qa.net
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
Effective Usage of SQL Server 2005 Database Mirroring 09th March 2007, SQL Server Open World www.sqlserver-qa.net
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
Effective Usage of SQL Server 2005 Database Mirroring 09th March 2007, SQL Server Open World www.sqlserver-qa.net
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
Disable DB Mirroring: Database mirroring requires AUTO_CLOSE OFF. 09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring
09th March 2007, SQL Server Open World www.sqlserver-qa.net Effective Usage of SQL Server 2005 Database Mirroring