Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 357
  • Last Modified:

SQL Server 2008 Cluster Install Issues On Windows 2003 (SQL Network Name)

Greetings,

I have had several failed attempts when attempting to install SQL Server 2008 Cluster on a windows 2003 active/passive cluster. Here's my issue. When I get to the point where I have to type a name for the SQL Network Name, I improvise a type a name like SQL2K8VRTL for example and the install completes with success but when I look in the cluster administrator tool the SQL Network name fails to start. I used the cluster admin account during installation and I still get the same error. Should I just use the virtual name created for the windows cluster instead of typing a name that does not already exist? Please advise.
0
Omega002
Asked:
Omega002
  • 6
  • 5
5 Solutions
 
65tdCommented:
Do not use the cluster network name.
In the SQL group is the IP address on line?
Is there a DNS name associated with the SQL IP?
SQL wants to register the SQL2K8VRTL  name it's self.

In the SQL group, one should have the at least the following resources:
IP
Network Name
Disk and SQL agent, SQL Server.
0
 
Omega002Author Commented:
So in order to use the SQL2k8VRTL name someone needs to create that name in DNS and assign an ip or can it have the same ip as the virtual name used for the windows cluster?
0
 
65tdCommented:
Let SQL attempt to populate an empty DNS entry, if does not then populate it.
If there is an entry in DNS SQL will not create the network name.

Do not use the default cluster group resources including network name and IP or quorum drive.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
65tdCommented:
should have one IP for each node and one heartbeat address per node and an IP for the default cluster group (Administrative cluster).

Then each new group or service such as SQL should have it's own group and resources such as Network name and IP, disk and application or service.
0
 
Omega002Author Commented:
So it's fine to create any SQL network name during the installation even though it does not exist in DNS? So if that is the case and it doesn't create the SQL network name in DNS after the installation is complete just have the network admin add the unique SQL network name into DNS and everything should be working?
0
 
65tdCommented:
Q1 yes
Q2 correct

What flavor of DNS is used, active directory integrated?
0
 
Omega002Author Commented:
Another question I have is that I have to run setup from second node after I complete the installation on the first node correct? In SQL Server 2005 you would only perform the installation on the first node and the installation is complete correct? So if I understand correct, SQL Server 2008 Cluster involves installation setup being executed on node1 then once completed you run installation setup on node2 correct?
0
 
Omega002Author Commented:
we use AD for DNS.
0
 
65tdCommented:
Is the SQL install files 2005 Enterprise?
SQL 2005 standard can be used in a cluster (two nodes only).

http://support.microsoft.com/kb/327518

Install notes for SQL 2k5 std:
http://technet.microsoft.com/en-us/library/cc719004(WS.10).aspx
0
 
Omega002Author Commented:
This is not SQL Server 2005 it's SQL Server 2008 Enterprise Edition RTM.
0
 
Omega002Author Commented:
No comments
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now