Effective Usage of SQL Server 2005 Database Mirroring

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

Topics Introduction Today’s Goals SQL Server 2005 High Availability features Database Mirroring concepts Usage and Practices Failover & Failback implementation Monitoring Mirroring Performance Conclusion Frequently Asked Questions Q & A

Introduction - Speaker Webmaster of www.sqlserver-qa.net & www.sqloogle.co.uk Been in the IT field over 15 years SQL Server DBA for over 10 years (since ver. 4.2) Contributing Editor, Writer & Moderator for www.sql-server-performance.com Currently, working full-time as Sr. DBA at a large Financial Enterprise focusing on SQL Server high availability, clustering, disaster recovery, and performance tuning. SQL Server MVP ( www.microsoft.com/mvp /) Participation in assorted forums such as MSDN, SQL Server magazine, dbforums and so on 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Today’s Goals Focus on what you can do, as a DBA, to ensure the highest availability of your mission-critical, production SQL Servers. How better Database Mirroring can help you to achieve the High Availability to the databases. Look at a series of configuration & best practices that every DBA should follow to help insure high SQL Server availability. Industry best practices & implementation. Prevention & Practices Selecting a HA Solution that suits the business needs. IT costs – planning, budget approval & implementation. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

SQL Server 2005 High Availability features SQL Server 2005 High Availability is a set of best practices and technologies designed to increase database availability through backups that help recover from catastrophic disasters, redundant database components engineered to prevent downtime, and redundant server implementation designed to minimize downtime. High Availability (HA) solutions: Failover Clustering Database Mirroring (supported from Service Pack 1 onwards) Log Shipping and Replication SQL Server 2005 database engine features (database mirroring) Enterprise Edition - Fully supported (failover partners must use the same edition) Standard Edition - Safety full only Workgroup Edition, SQL Express & SQL Express with Advanced services – Only as witness SQL Express and the Workgroup Edition can be used as a witness server, but they cannot be used as a partner server in database mirroring. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

SQL Server 2005 High Availability features Failover clustering and Database mirroring both provide the following: Automatic detection and failover, Manual failover and Transparent client redirect Constraints in Failover Clustering Operates at the server instance scope Requires certified hardware (HAL) Has no reporting on standby Utilizes a single copy of the database Does not protect against disk failure Database Mirroring benefits for the constraints above: Operates at the database scope Uses a single, duplicate copy of the database Uses standard servers Provides limited reporting on the mirror server by using database snapshots When operating synchronously, provides for zero work loss through delayed commit on the principal database. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

SQL Server 2005 High Availability features Database Mirroring - What is the advantage over Failover Clustering? You can mix & match database mirroring with a failover clustering. Database mirroring works easily between failover clusters and also between a failover cluster and a nonclustered host. Database mirroring & log shipping with Notification Services This combination can be used to provide high availability for your notification applications, you can maintain a standby server that you can bring online after failures or during server maintenance. Benefits of – increased data protection, increased availability of databases during any hardware or software patching. Configuration - High Protection & High Performance. No licensing cost to setup witness server. It is recommended that you first learn the High Performance configuration and then move to the High Protection configuration. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

SQL Server 2005 High Availability features Log shipping – this can be used as a supplement or an alternative to database mirroring. A key difference as compared to database mirroring. Capable to support multiple secondary databases with a single primary database. Can be useful only if data is accidentally changed on the primary database. Dependant upon the transaction log and shared backup location. Manual intervention is required in order to failover the primary database in the event of any failure on primary server. With SQL Server Management Studio you can view the Transaction Log Shipping status report at a monitor server, primary server, or secondary server. To see the most complete information about your log shipping configuration, view the report at the monitor server instance. An upgrade from a SQL Server 2000 log shipping configuration to SQL Server 2005 cannot be achieved as the Database Maintenance Plan Wizard, which was integral to log shipping in SQL Server 2000, is not used as part of the log shipping configuration in SQL Server 2005. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

SQL Server 2005 High Availability features Replication involves the Publisher, Distributor, and Subscriber Metaphor. Replication Scenarios – Central Publisher and with Remote Distributor. Publishing Subscriber & Central Subscriber. Multiple Publishers or Multiple Subscribers. Subscriptions. Pull, Push & Anonymous Subscriptions. Replication Agents. Snapshot, Log Reader, Distribution, Merge Agents. Timing, Latency, and Autonomy of Data with the methods of data distribution. SQL Server Replication Types. Snapshot Replication, Transactional Replication & Merge Replication. Backup and Recovery in a Replication Configuration. Alternate Synchronization Partners. Worldwide Sales and Marketing-Scenario with Data Replication. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Database Mirroring concepts What is - Database mirroring transfers transaction log records directly from one server to another and can quickly fail over to the standby server. An originating SQL Server 2005 instance continuously sends a database's transaction log records to a copy of the database on another standby SQL Server instance. Client connections - can code client applications to automatically redirect their connection information, and in the event of a failover, automatically connect to the standby server and database. Fast failover - with minimal data loss has traditionally involved higher hardware cost and greater software complexity. No dependency on proprietary hardware (cost and complexity), and easy to setup and manage. SQL Server 2005 supports database mirroring between 64 bit & 32 bit editions. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Database Mirroring concepts Terms involved: Principal – the server that holds a copy of database that is accessible to client applications at any given time. Mirror – the server that holds copy of database that is always in restoring state that is not accessible to the applications. Witness – the optional server that is useful to provide an automatic failover mechanism in case of any failure on principal server. Send Queue - a queue (principal) that builds up when the log records can’t be sent at the rate at which they are generated from principal to mirror. It is a part of the log that has not yet been sent to mirror server. Redo Queue – a queue (mirror) that builds up when the log records can’t be applied at the rate at which they are received from principal server. It is a part of log that remains to be applied to the mirror database to roll it forward. Endpoint : A SQL Server object that enables Principal, Mirror & Witness servers to communicate over the network. It encapsulates a transport protocol and a port number. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Database Mirroring concepts Terms involved: System databases cannot be a part of mirroring. Snapshot on mirror is possible for read-only purpose that is ideal for reporting requirements. Mixture – An instance can serve as the principal for one database, the mirror for another database, and the witness for yet another database. Encryption - Data between the principal and the mirror is transferred encrypted by default. Transaction safety level – that determines whether the changes on the principal database are applied to the mirror database synchronously or asynchronously. Two safety levels—OFF and FULL. Synchronous - the mirror server must synchronize the mirror database with the principal database. Speeds up the writes all of the incoming log records to disk as quickly as possible. Asynchronous – this sets up database mirroring with high performance. With safety OFF, the transaction is committed as soon as the principal server writes the log record to the local log and sends the log record to the mirror, without waiting for an acknowledgement from the mirror server. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Database Mirroring concepts Database Mirroring configuration: High Availability Supports automatic detection and automatic failover in the event of a disaster by requiring a third instance to act as a Witness server. “ full safety” form - If the Principal Database fails then the Witness will coordinate with the Mirror to have the Mirror database come online automatically to service client requests. High Protection Does not support automatic detection or automatic failover in the event of a disaster and it does not require or use a Witness. Still uses “full safety” - steps to configure High Protection are identical to the High Availability configuration with the exception of the setup of the Witness server. This should be used when automatic failover is not required and when more control on the failover scenario is desired. High Performance Does not support automatic detection or automatic failover in the event of a disaster and it does not require or use a Witness. Uses an asynchronous (“full safety off”) form of mirroring. With full safety off, changes are not required to be sent immediately to the Mirror Database. This allows the Principal Database to focus on client requests without the need to immediately and synchronously send the changes. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Database Mirroring concepts 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net Another configuration mode (possible) asynchronous mode with no witness server – although this is possible to setup it is not recommended because it combines the risk of data loss and split-brain scenario. Operating Mode Transaction Safety Transfer Mechanism Quorum Required Witness Server Failover type High Availability FULL Synchronous Yes Yes Automatic or Manual High Protection FULL Synchronous Yes No Manual High Performance OFF Asynchronous No No Forced

Database Mirroring concepts The mode is dependant on setting of Transaction Safety and Witness Server. The impact of the transaction safety level on performance is application dependent. 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. Standard Edition allows only the FULL transaction safety level. Configuration must be chosen depending upon the business requirement 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Depending on the transaction safety level and whether you have a witness, you can have automatic failover, manual failover, or both. Safety levels and failover options sequence: Failure occurs may be caused by hardware, storage, network, or power failure on the principal server. Failure is detected by mirror and witness Failure due to power loss are detected quickly within 1 second. Failure due to hardware issues such as storage disks will take bit longer to detect, as dependant upon the ping process between principal, mirror and witness servers. Default timeout is 10 seconds and can be changed using ALTER DATABASE SET PARTNER TIMEOUT statement. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Safety levels and failover options sequence: Redo process on mirror Remaining log in the redo queue of the mirror at the time of failure of the principal is applied on the mirror database to completely recover it. Decision to fail over (1 second) A coordination process with the witness and decides that the database should now fail over to the mirror. Mirror becomes principal Once remaining redo log is applied the mirror database is brought online and assumes the role of principal, that is available for application connections. Undo All uncommitted transactions in the transaction log are rolled back. Database state: SYNCHRONIZING, SYNCHRONIZED, SUSPENDED, PENDING_FAILOVER & DISCONNECTED. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Things to take care From the server perspective, the database failover time is the amount of time that it takes from the time the failure of the principal is detected to the time the mirror assumes the role of the principal. A major component of the database failover time can be the redo phase. Time to apply the redo records depends on the redo queue length and the redo rate on the mirror. SYSMON counters Redo Queue KB and Redo Bytes/sec to measure this performance. To accomplish roll forward, the SQL Server Database Engine processes log backups as they are restored, starting with the log that is contained in full backups, so the log backups after full backups is most important to reduce the redo phase time. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Things to take care The database might contain changes made by transactions that are uncommitted at the recovery point. So it is better to keep the transactions in smaller batches to avoid lengthy time during failover time for a mission-critical database. If redoing fails, the mirror server pauses the session by putting the database into the SUSPENDED state. The database owner must resolve the cause of the failure before resuming the session. Client connection string supplied by the client contains information that the data access provider uses to connect to the database. Connection string should contain the Network attribute to specify the network protocol. This ensures that the specified network protocol persists between connections to different partners. Recommended protocol for connecting to a mirrored database is TCP/IP {Network=dbmssocn;} 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Things to take care Ensure TCP/IP is enabled from SQL Configuration Manager all the instances in database mirroring. Named pipes can also be used, but a drawback is it does not use the TCP/IP retry algorithm, in many cases, a named pipes connection attempt may time out before connecting to a mirrored database. When Database Mirroring appears to be running smoothly – don’t let yourself get a false sense of security. Things may be running smoothly but this is when you’ll want to be on the highest alert. One way to measure the actual failover time is to use SQL Server Profiler [ Database Mirroring State Change event] on the principal and the mirror. The name of an endpoint is changed when the port changes. If SQL Server is listening on dynamic ports, the port can change, changing the endpoint name, and dropping the associated endpoint permissions. To avoid this security risk, do not set custom permissions on endpoints associated with dynamic ports, and do not change the order in which a TCP/IP endpoint occurs in the registry. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Usage and Practices Things to take care If the principal fails, the failover scenario depends on the transaction safety level and whether you have a witness. The length of the failover time depends upon the type of failure and the load on the database. For a given failure type (synchronous mirroring with witness) , it takes longer to complete the failover under load as compared to the no-load scenario. Changes in Recovery Model may be necessary Log Shipping supports Bulk-logged model If Log Shipped copy used as a safety store for recovering from erroneous user changes Create periodic Database Snapshots instead of delaying the application of log backups 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Failover & Failback implementation Preparing the Mirror for Failover It is better to use identical servers (in terms of CPU, memory, storage, and network capacity) as principal and mirror partners. Same service pack and patch levels for the operating system and SQL Server on both partners. Depending upon the rolling upgrades the service pack levels can be different between principal and mirror, but for steady state they must be identical. Ensuring that both servers have the same directory structure and SQL Server configuration eliminates the need for changes to these during or after the failover to the mirror partner. Ensure that all active SQL Server logins (and their permissions) on the principal server are also present on the mirror server. Ensure that all SQL Server Agent jobs, alerts, linked server definitions & SSIS packages are present in mirror server (disabled) and you may need them to enable in the event of a failover. TCP Endpoint on each server and configure authentication on endpoint with CONNECT permission appropriately. The above preparation lists are applicable to the system databases between the principal and mirror servers. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Failover & Failback implementation If there are multiple databases in an instance, you need to mirror each database individually. The recommended limit of 10 databases in 1 SQL instance is only approximate and not an exact number. The limit (memory and threads) can vary depending upon your application and workload. If your application consists of multiple databases, develop an alert mechanism to detect if one database fails over while others don’t. In this case you might need a manual failover of other databases. In some cases (High Availability mode) failover can occur automatically while in others it must be forced. To test the automatic failover you will shutdown the principal server and watch how the mirror server automatically comes online to handle requests. High Performance is the best configuration with which to start as it has the least impact to your production workload yet still offers a secondary database that’s close to current. Enable ALL of the threshold warnings for BOTH the principal and the mirror instance. Database Mirroring has a single WMI Event to which all changes are logged. To understand how the system works without the option of automatically failing over, try using database mirroring without a witness for a time. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Failover & Failback implementation Security of mirroring sessions can be controlled by configuring the listener ports used for communication between mirrored partners. Transaction Safety (SET TRANSACTION SAFETY) FULL : Transactions are forwarded synchronously (High Protection) OFF: Transactions are forwarded asynchronously Removing Witness Server (SET WITNESS OFF) Behavior of mirroring session after the witness is removed depends on the transaction safety level. Testing Failover procedure Using the SQL Server Management Studio is simple – a single click of the “Failover” button in the mirroring dialog and if you say yes to “failing over and disconnecting currently connected users”, then the failover occurs very easily. In similar using TSQL procedures is another straight forward solution that includes the catalog views, changing roles. Additionally, in High Protection, failover is not automatic and instead – must be forced. Initiate manual failover from principal database in order to switch partner roles. ALTER DATABASE <PrincipalDatabaseName> SET PARTNER FAILOVER Using the High Protection mode as the first implementation probably makes testing easier than jumping right into the High Availability mode. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Failover & Failback implementation Initiating Failover using SQL Server Management Studio : In the Object Explorer window, right-click on the PrincipalDB (Principal, Synchronized) database and choose P r operties . On the Database Properties - PrincipalDB dialog, select Mirroring from the Select a page pane. On the Mirroring page of the Database Properties - PrincipalDB window, click on the F ailover button to initiate the failover. On selection, a Database Properties message box will appear stating: Failing over Database Mirroring will swap the roles of the mirror and principal databases. The mirror database will become the principal database, and the current principal will become inaccessible. If you have just modified any properties in the Database Properties dialog box, those changes will be lost. In addition, SQL Server must close all other connections to the current principal database. Are you sure you want to fail over Database Mirroring to the mirror database and close all connections to the current principal database? Select Y es to confirm the failover. In the Object Explorer window, expand the Databases list (under the GALAXY1\EARTH connection). Right-click on Databases and select Re f resh . The PrincipalDB database on the former principal server should be listed as the mirror database after failover: PrincipalDB (Mirror, Synchronized / Restoring…) Expand the Databases list under the GALAXY1\MARS connection. Right-click on Databases and select Re f resh . The PrincipalDB database on the new principal server should be listed as: PrincipalDB (Principal, Synchronized) Return to the Database Monitor and notice the titles now – during the failover, the client application detected the network timeout and reconnected to the NEW principal. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Failover & Failback implementation W ith and W ithout W itness Witness is not the most important member of the database mirroring session. Witness server assists Principal or Mirror server in forming a quorum. If Principal server cannot connect to mirror server, still the quorum consists with Witness to keep up the database in service. In case Principal server is down then Witness initiates failover where the Mirror can take on the role of new principal server. When the partner servers cannot see each other, the partner servers contact the witness to see whether the witness can contact the other partner and verify that a failure has occurred. Witness is not a single point of failure. The location of Witness is dependant upon your network availability to avoid losing two different servers, and therefore quorum, if the power system fails. General recommendation of Witness location is to accompany Principal. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Monitoring Mirroring Performance In addition to using the Database Mirroring Monitor and dbmmonitor, you can use stored procedures to monitor a mirrored database and set up alerts on monitored performance variables. SYSMON counters on each partner server helps you to monitor the performance of database mirroring, few of them are important to watch: SQLServer:Database Mirroring Databases - Transactions/sec On Principal server Log Bytes Sent/sec Log Send Queue KB Log Bytes Flushed/sec Disk Write Bytes/sec On Mirror server Redo Bytes/sec Redo Queue KB Disk Write Bytes/sec Other Logical Disk counters 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Monitoring Mirroring Performance Rolling upgrade Upgrade the mirror first Failover Upgrade the new mirror Failover again If using asynchronous mirroring Upgrade the mirror first Wait for a low activity window Switch to synchronous, and wait till SYNCHRONIZED Follow process similar to one above Switch back to asynchronous SQL Server Profiler trace: Database Mirroring State Change event class Audit Database Mirroring Login event class 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Monitoring Mirroring Performance Troubleshooting Database mirroring does not regularly check the components on which Sqlservr.exe relies to verify whether they are functioning correctly or have failed. Failures in databases other than the mirrored database are not detectable in a database mirroring session. Moreover, a data disk failure is unlikely to be detected, unless the database is restarted because of a data disk failure. If database mirroring is not working, check the following to make sure the configuration is correct: Look at the column STATE_DESC in the catalog view sys.database_mirroring_endpoints . Endpoints compatible encryption settings Look at the column IS_ENCRYPTION_ENABLED in the catalog view sys.database_mirroring_endpoints Look at the columns TYPE_DESC and ROLE_DESC respectively of the catalog view sys.database_mirroring_endpoints for the correct type and roles. Ensure port numbers of the endpoints are the same as the corresponding port numbers specified in the SET PARTNER statements. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Monitoring Mirroring Performance Account under which the SQL Server instance is running has the necessary CONNECT permissions. If SQL Server runs under a different user on one or more of these servers, then you need to grant CONNECT permission on the endpoint of a server to the login account of the other servers. Make sure the port that is used for database mirroring endpoints is opened through the firewall, if used. Critical - speed of error detection and, therefore, the reaction time of the mirroring session to a failure, depends on whether the error is hard or soft. Few network components and some IO subsystems, have their own time-outs to determine failures. Mirroring does not protect against problems specific to client accessing the servers, such as public network adapter on any partner server. Database mirroring failover and failback procedures are dependant on the network components and server hardware in addition to the server/database configuration. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Conclusion Measures & Practices The operational tasks related to the data center span the full life-cycle of the data services it helps to provide, from planning, through building and deployment, to operation. Managed data stores use database mirroring and therefore when performance becomes an issue, the IT operations team can add new higher specification servers. What’s new for DBA: Role of the database administrator is changing, thoughts on the relevance of 64-bit and Itanium with respect to Business Intelligence (BI), and the very on-topic advances in High Availability, such as Database Mirroring and Log Shipping technology in SQL Server 2005 and its implications for disaster recovery. Database Mirroring can be set to fail-over and recover automatically. Indeed, db mirroring offers a substantial increase in availability over standard log shipping, by maintaining a hot-standby server where changes are reflected real-time, and applications can recover quickly with minimal, if any, intervention. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Conclusion The performance of database mirroring is very closely associated with the type of application, transaction safety level, and network performance. The network plays a very important role in a database mirroring environment. When used with a high-bandwidth and low-latency network, database mirroring can provide a reliable high-availability solution against planned and unplanned downtime. Across geographically distant data centers, database mirroring can provide the foundation for a disaster-recovery solution. Do not forget to test and plan for any sort of new introduction to your High Availability ranch, even changes in Database Mirroring mode. 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Frequently Asked Questions Support for Database Mirroring prior to SQL Server 2005 SP1. Can I mirror between multiple virtual servers in a cluster? What is the slowest network that I can use with mirroring? What and Why don’t some technologies work seamlessly after a failover? How to disable database mirroring for a particular database, is it possible? What is the usage of WITNESS instance in Database Mirroring setup? Is it recommended to use 32-bit server as Witness for a 64-bit Database Mirroring Partner server? 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Questions & Answers I’ll do my best to answer your questions. If you don’t get your questions answered today, post them at: SSP Forums & MSDN Forums or view Blogs Additional Database Mirroring Resources Database Mirroring in SQL Server 2005 by Ron Talmage - Whitepaper Implementing Database Mirroring, series for IT Professionals, presented by Kimberly L. Tripp, SQLskills.com – Webcast SQL Server 2005 Books Online Refresh, February 2007 – Link High Availability resources – SSP & SSQA 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Thank you and have a great day ahead . Feedback : Please fill out evaluation forms 09th March 2007, SQL Server Open World Effective Usage of SQL Server 2005 Database Mirroring - www.sqlserver-qa.net

Effective Usage of SQL Server 2005 Database Mirroring

More Related Content

What's hot (19)

Viewers also liked (20)

Similar to Effective Usage of SQL Server 2005 Database Mirroring (20)

More from webhostingguy (20)

Effective Usage of SQL Server 2005 Database Mirroring

Editor's Notes