Database Mirroring Automating Failover for Multiple SQL Server Databases

63 阅读 0 评论 42 点赞

我是靠谱客的博主如意玉米，最近开发中收集的这篇文章主要介绍Database Mirroring Automating Failover for Multiple SQL Server Databases ，觉得挺不错的，现在分享给大家，希望可以做个参考。

概述

Written By: Edgewood Solutions Engineers -- 8/18/2008 -- 6 comments

Win SQL Server Books - click here

Problem
Database Mirroring was released with SQL Server 2005 and is becoming a popular choice for a failover solution. One of the big issues with Database Mirroring is that the failover is tied to one database, so if there is a database failure the mirrored server takes over for this one database, but all other databases remain functional on the primary server. The drawback is that more and more applications are being built where multiple databases make up the application, so if only one of the databases fails over the other database will still be functional on the principal server, but the application won't work. How can I be notified when this happens and make all of the databases failover?

Solution
As with just about all functions in SQL Server, there is a way to get alerts or check for events that occur when a database mirroring failure occurs. Unfortunately this event notification for Database Mirroring is not as straight forward as you would think, but it can be done.

For database mirroring you have the choice of using trace events or you can setup a SQL Server Alert to check for a WMI (Windows Management Instrumentation) event for Database Mirroring state changes. Before we get started there are a few things you need to do:

Preliminary Steps

The mirrored databases and the msdb database must have service broker enabled. This can be checked with this query

SELECT name, is_broker_enabled
FROM sys.databases

If the service broker value is not set to 1 you can turn this on by issuing this command for each database.

ALTER DATABASE msdb SET ENABLE_BROKER

If SQL Server Agent is running this command will not complete, so you will need to stop SQL Server Agent, run the above command and then start SQL Server Agent again.

Lastly, if SQL Server Agent is not running you will need to start it.

Creating the Alert

To setup the alert we are going to do this just like any other alert, but we are going to be using the "WMI event alert" type.

To create the alert expand the SQL Server Agent tree and right click Alerts and select "New Alert".

On the New Alert screen we are going to change the type to "WMI event alert". Another thing that you will notice is the Namespace that is being queried. By default SQL Server will select the correct namespace based on the instance of SQL Server you are working with.

For the query we are using the following:

SELECT * FROM DATABASE_MIRRORING_STATE_CHANGE WHERE State = 7 OR State = 8

This data is read from WMI and whenever the database mirroring state changes to either 7 (manual failover) or 8 (automatic failover) the job or notification will be fired.

In addition, you can further define the query for a particular database such as:

SELECT * FROM DATABASE_MIRRORING_STATE_CHANGE WHERE State = 8 AND DatabaseName = 'Test'

For additional information you can read about DATABASE_MIRRORING_STATE_CHANGE in books online.

Below is a list of the different state changes that can be monitored. Additional information can be found here Database Mirroring State Change Event Class.

0 = Null Notification
1 = Synchronized Principal with Witness
2 = Synchronized Principal without Witness
3 = Synchronized Mirror with Witness
4 = Synchronized Mirror without Witness
5 = Connection with Principal Lost
6 = Connection with Mirror Lost
7 = Manual Failover
8 = Automatic Failover
9 = Mirroring Suspended
10 = No Quorum
11 = Synchronizing Mirror
12 = Principal Running Exposed
13 = Synchronizing Principal

On the Response screen we can setup how to handle this event when it occurs. You can either setup a job that runs when the Alert is fired and/or a notification to an operator that has been setup.

Lastly, you can setup additional options for the alert as shown below.

Example Setup

So let's say you have three databases (Customer, Orders, Log) that are part of an application and if one of the databases automatically fails over you want the other two databases to failover as well. In addition, this mirroring setup includes a Witness server so if a failure occurs the failover is automatic.

Here is how this could be setup.

First we setup the Alert to look at just these three databases.

Then we tell the alert which job to run.

Then we need to create the job "Failover Databases" which will be run when this alert is fired.

For the SQL Agent job "Failover Databases" the jobs steps would look something like the following:

IF EXISTS (SELECT 1 FROM sys.database_mirroring WHERE db_name(database_id) = N'Customer' AND mirroring_role_desc = 'PRINCIPAL')
ALTER DATABASE Customer SET PARTNER FAILOVER
GO

IF EXISTS (SELECT 1 FROM sys.database_mirroring WHERE db_name(database_id) = N'Orders' AND mirroring_role_desc = 'PRINCIPAL')
ALTER DATABASE Orders SET PARTNER FAILOVER
GO

IF EXISTS (SELECT 1 FROM sys.database_mirroring WHERE db_name(database_id) = N'Log' AND mirroring_role_desc = 'PRINCIPAL')
ALTER DATABASE Log SET PARTNER FAILOVER
GO

The ALTER DATABASE command above forces the failover to the mirrored server for the other databases that did not automatically get flipped. This is the same as if you clicked on the "Failover" button in the GUI.

Next Steps

Now that you have an idea how you can use the WMI events to check for mirror state changes do some testing on your servers to see if this is something you could use.
Each time a database fails over it will kick off the alert, so if there are multiple failovers it will attempt to run the "Failover Databases" job multiple times.
You also would need to think about how you would want this to run. You may want an automated failover from the primary server to the secondary server, but you may only want to be notified if the failure goes from the secondary to the primary server.
Although this may not be an ideal solution, it does allow you to get all of your databases on the same server. Since database mirroring is still at the database level there is no guarantee that all or your transactions will stay in synch across multiple databases whether you use this approach or not.