To connect to a database mirroring session, a client can use either SQL Server Native Client or .NET Framework Data Provider for SQL Server. When configured for a SQL Server 2008 database, these data access providers both fully support database mirroring. For information about programming considerations for using a mirrored database, see Using Database Mirroring. In addition, the current principal server instance must be available and the login of the client must have been created on the server instance. For more information, see Troubleshooting Orphaned Users. Client connections to a database mirroring session do not involve the witness server instance, if one exists.
In This Section
-
Making the Initial Connection to a Database Mirroring Session
-
Introduces initial partner name and failover partner name, explains how data access providers make the initial connection to a mirrored database, and describes the connection-string attributes for connecting to a mirrored database.
-
Connection Retry Algorithm (for TCP/IP Connections)
-
Describes the connection retry algorithm for TCP/IP connections from clients running Windows XP or later versions.
-
Reconnecting to a Database Mirroring Session
-
Describes reconnecting to a mirrored database if an established connection to a database mirroring session fails for any reason and the impact of redirection on a client application.
-
The Impact of a Stale Failover Partner Name
-
Discussed the impact of a database administrator changing one of the mirroring partners for a mirrored database.
See Also