DATABASES: SQL SERVER 2005
Dell Power Solutions,
February 2006. Copyright © 2006 Dell Inc. All rights reserved
DELL POWER SOLUTIONS
mode and one in active/active mode. In a failover cluster envi-onment, SQL Server 2005 offers several additional features andmprovements compared to SQL Server 2000:
Support for multinode clustering:
Standard Edition allowsup to two-node clustering and Enterprise Edition up to eight-node clustering.
Support for SQL services:
Analysis Services feature offersmulti-instance support and full-text indexing.
System Configuration Check automati-cally detects and installs SQL Server as virtual servers acrossthe nodes in the cluster.
Database mirroring is designed to augment the availability of SQLServer 2005. With this feature, transactions to a database hostedon a SQL Server instance, referred to as the principal, can be con-inuously duplicated in real time onto a copy hosted on anothernstance, referred to as the mirror. The principal and mirror serversare considered partners in a database mirroring session. Transac-ions (such as insertions, updates, and deletions) on the principaldatabase are duplicated by continuously sending transaction logecords to the mirror over the network (see Figure 2).The mirror receives the log records continuously and restoreshem. If the principal or mirror server incurs a failure, the mirror-ng session is disconnected. Before starting the mirroring session,administrators must initialize the mirror database from a principaldatabase full-restore with the NORECOVERY option.Besides the primary and mirror, a mirroring session may includean optional third server, referred to as the witness. The witnessserver enables automatic failover after a principal server failure bypromoting the mirror to function as the principal. Using a witnessserver helps achieve a quorum and prevents accidental promotionof the mirror database that results from communication failuresbetween the principal and mirror.Database mirroring requires the following configuration:
he primary and mirror databases must be hosted on sepa-ate SQL Server 2005 instances.
he principal database must be set to the Full Recovery model,ot the Bulk-Logged Recovery or Simple Recovery model.Database mirroring can be configured in any of the followingthree operating modes based on transaction safety level and thepresence of a witness server:
In this mode, log records are trans-erred synchronously from the principal database to theirror. The principal waits for an acknowledgment from theirror before “hardening” log records to its disk. In additionto providing synchronous transfer, this mode uses a witnessserver to enable automatic failover.
This mode is similar to the high-availability mode except that it does not support a witnessserver, and thus automatic failover is not possible. However,failover can be performed manually to promote the mirrordatabase. Because the log records are transferred synchro-ously in this mode, the mirror database is synchronous andconsistent with the principal.
In this mode, log records aretransferred asynchronously from the principal to the mirrordatabase. The principal does not wait for an acknowledg-ent from the mirror before “hardening” its logs to the disk,
Figure 1. Failover cluster configurations for SQL Server 2005
SQL Server 2005db1db2SQL Server 2005HeartbeatLAN
SQL Server 2005db1SQL Server 2005HeartbeatLAN
Figure 2. Database mirroring for database db1 in high-availability mode
db1db2db3SQL Server 2005db5db6SQL Server 2005SQL Server 2005db1
Transaction log records Log recovery