Quick facts about the capability of SQL server 2000 cluster failover and resources

Quick facts about the capability of SQL server 2000 cluster failover:
1) The SQL Server 2000 Analysis Services (OLAP and data mining) component is not supported on a failover cluster. For more information, see the Knowledge Base article "254321 – Clustered SQL Server Do’s, Don’ts and Basic Warnings" at http://support.microsoft.com/default.aspx?scid=kb;en-us;254321&sd=tech
For How to cluster SQL Server 2000 Analysis Services in Windows 2000 and Windows Server 2003, see: http://support.microsoft.com/kb/308023/
2) SQL Mail is not fully supported when used on a SQL Server failover cluster because MAPI is not cluster-aware
3) Named Pipes Support Cannot Be Removed on a Virtual Server That Is Running SQL Server 2000 SP3. But can be removed on SP3a or SP2. http://support.microsoft.com/kb/831127/
4) You must set SQL Server services startup type to Manual. The use of Automatic startup is not supported for use with Virtual SQL Servers.
5) SQL Server is not supported for Terminal Services in application server mode. http://support.microsoft.com/kb/327270/
6) We recommend that you use SQL Server Enterprise Manager, SQL Server Services applet, or Cluster Administrator to start and to stop SQL Server 2000 virtual server services. Although you can use Service Control Manager or Control Panel/Service to start and to stop the services without damaging the registry, these options will not cause the services to stay in a stopped state. Instead, the services will be detected by the clustered server and you will receive multiple event ID 17052 error messages in you SQL Server that are similar to the following:
[sqsrvres] CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: service stopped while waiting for QP
[sqsrvres] OnlineThread: Error 1 bringing resource online
After you receive these error messages, SQL Server will be restarted by the cluster service.This behavior is expected for these types of errors.
7) Windows 2000 Datacenter Process Control and SQL Server 2000 Failover Clustering
Do not use Process Control to modify SQL Server virtual server configurations. Process Control is not a cluster-aware application, and in the event of a failover, the virtual server modified on one node will not carry over the process control constraints from the failed node automatically. Use SQL Server Enterprise Manager and the other SQL Server-supplied tools to modify the SQL Server virtual server configuration.
6) SQL 7.0: Full text search is not available to clustered SQL Server 7.0 servers
SQL Server 2000 Failover Clustering official resource: http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
This entry was posted in SQL server. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s