Summary
This article describes the different versions of SQL Server using SQL Server clustered servers for a number of important issues and not the issues.
IMPORTANT:
All is still by SQL Server 6.5 and SQL Server 7.0 using the cluster function as soon as possible when conditions allow users to upgrade to SQL Server 2000. SQL Server 2000 Enterprise Edition with failover clustering to support the following tools, features and components:
Microsoft Search Service
Multiple Instances
SQL Server Enterprise Manager
Service Control Manager
Copy
SQL Profiler
SQL Query Analyzer
NOTE: Microsoft Product Support Services (PSS) support for SQL Server failover cluster, such as the following Microsoft Knowledge Base article:
327518 SQL Server failover cluster in Microsoft support policy
SQL Server with Microsoft Cluster Server (MSCS) in combination, you must install the Enterprise Edition to provide support.
More
Start and stop SQL Server services
SQL Server 6.5 and SQL Server 7.0 virtual server
If you try any other means (for example, from the Control Panel, SQL Service Manager or SQL Enterprise Manager) to start or stop the service, the registry may be damaged, and you may need to cancel on the SQL Server or completely reinstall gathered SQL Server.
Services start not the correct service account the most common sign is displayed as ASCII characters in a pile of clutter.
From the command line if you need to start SQL Server, you must first use the Cluster Administrator or Cluster.exe tool to enable SQL Server, SQL Executive or the SQL Agent service offline.
When you start SQL Server from the command line, it will use the virtual server name to connect. A prerequisite for local connection is a resource from which you originally installed by the SQL Server node owned.
SQL Server 2000 virtual server
[Sqsrvres] CheckServiceAlive: Service is dead
[Sqsrvres] OnlineThread: service stopped while waiting for QP
[Sqsrvres] OnlineThread: Error 1 bringing resource online
When you receive these error messages, the Cluster service will restart the SQL Server. It is these types of errors expected behavior.
SQL Enterprise Manager
SQL Server 6.5 and SQL Server 7.0 virtual server
239885 How to change the clustered SQL Server service account on the computer
Warning: If you are unable to article Q239885 in accordance with the instructions, you may need to manually completely remove two nodes from the SQL Server, and then ensure that the SQL Server database security, the re-install the SQL Server.
If the SQL Server service account is not a cluster administrator account, then the management of shared any node in the cluster can be removed at no. Management must share the available cluster, SQL Server to work properly.
SQL Server 2000 virtual server
SQL Server 2000 Analysis Services (OLAP)
308023 How Windows 2000 and Windows Server 2003 will join the SQL Server 2000 Analysis Services cluster
SQL Connection
SQL Server 6.5 and SQL Server 7.0 virtual server
Warning: The SQL Server 6.5 in any changes to network settings on the SQL Server must be canceled after gathering, such as the following Microsoft Knowledge Base article:
189037 BUG: SQL Setup will not change the SVS of security and network support options
The connection or configure clustered SQL Server server connectivity issues commonly encountered additional information, please see the following article in Microsoft Knowledge Base:
273673 SQL Virtual Server client connections description
235987 SQL Server 7.0-based virtual server only supports the use of a TCP / IP address
244980 How to change the SQL Server virtual server's network IP address
187 708 socket cluster can not connect to the SQL virtual server
Multiple listening TCP / IP port
If you need more than listening TCP / IP port, you need to run the Cluster Wizard in the registry prior to the following modifications.
WARNING: Using Registry Editor incorrectly can cause serious problems that may need to reinstall your operating system. Microsoft can not guarantee that you can solve problems that result from using Registry Editor incorrectly caused the problem. Use Registry Editor at your own risk.
1, start the Registry Editor (Regedt32.exe).
2, in the following registry key value to find ListenOn: HKEY_LOCAL_MachineSoftwareMicrosoftMSSQLServerMSSQLServer
3, in the Edit menu, click Multi String, and enter other listening port. For example, to add port 1435, enter the following, and then click OK: SSMSSO70, 1435
4, quit Registry Editor.
Here you may add the other port of some examples:
SSMSSO70, 1436
SSMSSO70, 1437
Test your connectivity ports added, and then continue to use the cluster wizard.
SQL Server (all versions) and WINS configuration
193 890 recommended for use on Microsoft Cluster Server WINS configuration
195462 Microsoft Cluster Server for WINS registration and IP address problems
Do not clustered SQL Server servers or other Microsoft Cluster Server (MSCS) resources, add static entries in WINS; this in the following Microsoft Knowledge Base article describes:
217 199 static WINS entries cause the network name of the Offline
Clustered SQL Server server performance counters
When the system first starts, you must find the SQL Server extension counters. In SQL Server 6.5, by default, the counter DLL is located in \ MssqlBinn directory. Because until all MSCS resources are online to access the SQL Server cluster installation of the drive, so the system can not find the counter when you first start.