SQL Server 2000 & 2005 Clustering

Step 16 – Licensing Mode

In the Choose Licensing Mode dialog box, choose the right licensing scheme, enter the proper value, and click Continue.

Step 17 – Setup Notification

A setup notification box will now appear as the SQL Server 2000 virtual server is installed.

Step 18 – Setup Complete

In the Setup Complete dialog box, click Finish. If prompted to restart your servers, make sure you reboot all nodes of your cluster.


Chapter 10 – What is New with SQL Server Clustering on Windows 2003

Security Patch – Server Accessibility

If latest security patches are not installed on SQL Server, you may see following error message in event log.

You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer’s vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000.

Once SQL Server is patched up with latest security patch, it is available to listen to the TCP/IP and UDP ports.

Increased Nodes

You can have up to 8-node clustering in Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition.

Clustering by Default

On Windows 2003 server system, clustering is installed by default; you only need to configure a cluster with Cluster Administrator.

Restart Not Required

You no longer need to restart the computer after you install or uninstall clustering. Clustering and associated drivers can be started and stopped dynamically.

New Configuration Log File

New configuration process with increased analysis displayed on the screen and to the following log file:


Disk Corruption Log File

When disk corruption is suspected, the Cluster service reports the results of the CHKDSK command-line utility in several places. Results are logged in the Application log and the Cluster.log file. In addition, the Cluster.log file references a log file in which detailed CHKDSK output is recorded.


Cluster Log Error Levels

The Cluster log readability is improved by adding error levels (similar to Event logs) that can help identify problem areas:

  • Info = Informational Entries

  • Warn = Warning Entries

  • Err = Error Entries

Cluster Log Improved

Cluster logs now display the server’s local time in a log entry when Windows Clustering starts. This feature assists you when you are comparing Event log entries to Cluster logs.

Multi-Node Cluster Without a Common Shared Disk

In Windows Server 2003, there is a new quorum-capable resource name “Majority Node Set” (MNS). With MNS, you can configure a multi-node cluster without using a common shared disk.



No comments yet... Be the first to leave a reply!