Consider the following scenario:
- You have a Microsoft .NET Framework-based application that enables fast database mirroring between two servers that are running Microsoft SQL Server 2005.
- The mirror partner is a named instance of SQL Server. This named instance contains an alias in the SQL Server 2005 Configuration Manager client tool.
- The mirror partner server is connected to a nondefault port.
- The connectivity to the principal server is lost. Then, the application tries to connect to a mirror partner server.
- The.NET Framework-based application specifies an alias of the mirror partner server instead of the full server name and port number.
- Specify the full server name and the port number in the Failover Partner attribute.
- Enable the mirror partner server to run while it is connected on the default port. The default port number is 1433.
- Enable User Datagram Protocol (UDP) traffic to the mirror partner server over port number 1434.
You can specify the mirror partner server by using the Failover Partner attribute. The simplest way to determine the server instance is by its system name. For example, you can use the following format:
Article ID: 941526 - Last Review: Dec 3, 2007 - Revision: 1