694
Part V: Enterprise Data Management
■ (^) All the SQL Servers in database mirroring confi guration need to trust each other.
If they are on the same domain, you need to ensure that each SQL Server login can
connect to the other mirroring SQL Server and have CONNECT permission on the
endpoints. If the SQL Servers do not trust each other, you need to use certifi cates
for the communication between the servers.
Best Practice
Use a private high-speed network between the principal and mirror servers to reduce the network
bandwidth and impact on other users. SQL Server 2012 helps reduce the network bandwidth with the
log compression feature.
Configuring Database Mirroring Using Management Studio
The following steps confi gure database mirroring using SQL Server Management Studio:
- In the Object Explorer on the principal server in SQL Server Management Studio,
right-click the principal database, and select Properties. - On the Options page, verify that the recovery model is full.
- On the Mirroring page, click the Confi gure Security button to launch the Confi gure
Database Mirroring Security Wizard. Click Next to begin the wizard. This wiz-
ard enables you to confi gure the security of the principal, mirror, and witness
(opt ional) ser vers. - On the Include Witness Server page, click Yes if you want to operate database mir-
roring in synchronous (high-safety) mode with automatic failover. For other oper-
ating modes (high-safety without automatic failover and high-performance mode),
click No. - On the Choose Servers to Confi gure page, as shown in Figure 27-3, ensure that
the Witness server instance check box is checked. Click Next to continue. If you
selected No in the previous step, you will not see this page. - The next page is the Principal Server Instance page, as shown in Figure 27-4. As
discussed earlier, communication between the servers participating in database
mirroring is accomplished over TCP endpoints. Each server requires its own, dedi-
cated database mirroring endpoint. Each endpoint listens on a unique TCP/IP port.
The default port is 5022, as shown in Figure 27-4 is 5022. For security reasons,
it is recommended to use a nondefault port. You cannot change the port number
from here, but it is confi gurable using the alter endpoint syntax later. Also,
by default, the check box for Encrypt data sent through this endpoint is selected.
Have this check box selected to ensure that the data transferred across the network
is encrypted. If for any reason you do not need encryption, uncheck this box. You
can also change the endpoint name on this page. Click Next to continue.
c27.indd 694c27.indd 694 7/31/2012 9:50:26 AM7/31/2012 9:50:26 AM
http://www.it-ebooks.info