Allow a Database Mirroring Endpoint to Use Certificates for Outbound Connections (Transact-SQL)
This topic describes the steps for configuring server instances to use certificates to authenticate outbound connections for database mirroring. Outbound connection configuration must be done before you can set up inbound connections.
All mirroring connections on a server instance use a single database mirroring endpoint, and you must specify the authentication method of the server instance when you create the endpoint.
The process of configuring outbound connections, involves the following general steps:
In the master database, create a database Master Key.
In the master database, create an encrypted certificate on the server instance.
Create an endpoint for the server instance using its certificate.
Back up the certificate to a file and securely copy it to the other system or systems.
You must complete these steps for each partner and the witness, if there is one.
The following procedure describes these steps in detail. For each step, the procedure provides an example for configuring a server instance on a system named HOST_A. The accompanying Example section demonstrates the same steps for another server instance on a system named HOST_B.
To configure server instances for outbound mirroring connections (On HOST_A)
On the master database, create the database Master Key, if none exists. To view the existing keys for a database, use the sys.symmetric_keys catalog view.
To create the database Master Key, use the following Transact-SQL command:
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<1_Strong_Password!>'; GO
Use a unique, strong password, and record it in a safe place.
In the master database, create an encrypted certificate on the server instance to use for its outbound connections for database mirroring.
For example, to create a certificate for the HOST_A system.
If you intend to use the certificate for more than one year, specify the expiry date in UTC time by using the EXPIRY_DATE option in your CREATE CERTIFICATE statement. Also, we recommend that you use SQL Server Management Studio to create a Policy-Based Management rule to alert you when your certificates are expiring. Using the Policy Management Create New Condition dialog box, create this rule on the @ExpirationDate field of the Certificate facet. For more information, see Administer Servers by Using Policy-Based Management and Securing SQL Server.
USE master; CREATE CERTIFICATE HOST_A_cert WITH SUBJECT = 'HOST_A certificate for database mirroring', EXPIRY_DATE = '11/30/2013'; GO
For more information, see CREATE CERTIFICATE (Transact-SQL).
To view the certificates in the master database, you can use the following Transact-SQL statements:
USE master; SELECT * FROM sys.certificates;
For more information, see sys.certificates (Transact-SQL).
Ensure that the database mirroring endpoint exist on each of the server instances.
If a database mirroring endpoint already exists for the server instance, you should reuse that endpoint for any other sessions you establish on the server instance. To determine whether a database mirroring endpoint exists on a server instance and to view its configuration, use the following statement:
SELECT name, role_desc, state_desc, connection_auth_desc, encryption_algorithm_desc FROM sys.database_mirroring_endpoints;
If no endpoint exists, create an endpoint that uses this certificate for outbound connections and that uses the certificate's credentials for verification on the other system. This is a server-wide endpoint that is used by all mirroring sessions in which the server instance participates.
For example, to create a mirroring endpoint for the example server instance on HOST_A.
CREATE ENDPOINT Endpoint_Mirroring STATE = STARTED AS TCP ( LISTENER_PORT=7024 , LISTENER_IP = ALL ) FOR DATABASE_MIRRORING ( AUTHENTICATION = CERTIFICATE HOST_A_cert , ENCRYPTION = REQUIRED ALGORITHM AES , ROLE = ALL ); GO
For more information, see CREATE ENDPOINT (Transact-SQL).
Back up the certificate and copy it to the other system or systems. This is necessary in order to configure inbound connections on the other system.
BACKUP CERTIFICATE HOST_A_cert TO FILE = 'C:\HOST_A_cert.cer'; GO
For more information, see BACKUP CERTIFICATE (Transact-SQL).
Copy this certificate using any secure method you choose. Be extremely careful to keep all of your certificates secure.
The example code in the preceding steps configure outbound connections on HOST_A.
You now need to perform the equivalent outbound steps for HOST_B. These steps are illustrated in the following Example section.
The following example demonstrates configuring HOST_B for outbound connections.
USE master; --Create the database Master Key, if needed. CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<Strong_Password_#2>'; GO -- Make a certifcate on HOST_B server instance. CREATE CERTIFICATE HOST_B_cert WITH SUBJECT = 'HOST_B certificate for database mirroring', EXPIRY_DATE = '11/30/2013'; GO --Create a mirroring endpoint for the server instance on HOST_B. CREATE ENDPOINT Endpoint_Mirroring STATE = STARTED AS TCP ( LISTENER_PORT=7024 , LISTENER_IP = ALL ) FOR DATABASE_MIRRORING ( AUTHENTICATION = CERTIFICATE HOST_B_cert , ENCRYPTION = REQUIRED ALGORITHM AES , ROLE = ALL ); GO --Backup HOST_B certificate. BACKUP CERTIFICATE HOST_B_cert TO FILE = 'C:\HOST_B_cert.cer'; GO --Using any secure copy method, copy C:\HOST_B_cert.cer to HOST_A.
Copy the certificate to the other system using any secure method you choose. Be extremely careful to keep all of your certificates secure.
After you set up outbound connections, you must configure inbound connections on each server instance for the other server instance or instances. For more information, see Allow a Database Mirroring Endpoint to Use Certificates for Inbound Connections (Transact-SQL).
For information on creating a mirror database, including a Transact-SQL example, see Prepare a Mirror Database for Mirroring (SQL Server).
For a Transact-SQL example of establishing a high-performance mode session, see Example: Setting Up Database Mirroring Using Certificates (Transact-SQL).