BUG: Incorrect Reference to the Second Virtual Server Instance Name (289107)


The information in this article applies to:

  • Microsoft SQL Server 2000 Enterprise Edition
This article was previously published under Q289107
BUG #: 352249 (SHILOH)

SYMPTOMS

In Microsoft SQL Server Books Online, in the "Failover Clustering Example" topic, there is an incorrect reference to the second virtual server instance name in the illustration that is shown.

SQL Server 2000 Book Online states:

"Run the Setup program again on CLUSTERNODEB. Create a new virtual server named "SQLCLUSTB" (in a different Microsoft Cluster Service (MSCS) cluster group) and install an instance named "Inst1" that can run on both CLUSTERNODEA and CLUSTERNODEB. From this point forward, connect to the server by specifying SQLCLUSTB\Inst1 as the connection string."

Correction

In the illustration that is shown in the example, the clients are instructed to connect to "SQLCLUSTB" as the second virtual server instance, which is incorrect. The correct second virtual server instance is SQLCLUSTB\INST1.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.
Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbBug kbpending KB289107
©2004 Microsoft Corporation. All rights reserved.