This is the last part of the series. Once you have configured windows cluster and MSDTC, installing SQL is piece of cake. I already mentioned in part 1 that you have to download ISO (SQLEVAL.ISO) which we would need to attached as CD drive which would have setup files. I have copied the image on E:\Virtual Server\SQLEVAL.ISO
We also need to create domain account and domain groups in domain controller. So, logon to domain controller. Go to Start > Run > DSA.msc and follow below screen-shots.
Give the details of account (i.e. SQLSVC)
Set the password after clicking next button. Make sure that "Password never expires" is checked and "User cannot change password" is checked.
One account is created, lets add a Group and add SQLSVC into the group.
Give Group Name "SQL Admin Groups"
Right click on "SQL Admin Groups" properties and add "members"
Now you are done with Domain controller.
Now, let's mount ISO image to MyNode1 and MyNode2. To do this, go to Virtual server console.
Click on CD/DVD and fill details as below
Above has to be done on both the nodes. Once you do that, you can see SQL Installation CD mounted on MyNode1 and MyNode2.
Lets Start SQL setup now.
Now we are done with the setup and we should see the resources in cluster admin under SQL Group.
Any feedback is greatly appreciated.
Great document! I was getting a problem with MSDTC failing at failover, your MSDTC guidance got that fixed. Thanks
Great series! Thank you for the work you put into all five articles!
One question: you mention the previous creation of the user, sqlsvc, and the group,SQL Admin Groups. But I cannot find that reference anyway else in the series. Are there any specifics to their creation? This is exactly where sql setup is failing on me, as it cannot 'see' and verify either the user or the group.
Any help would be appreciated.
Thanks for the feedback. I have added details to created domain account and group in the beginning of 5th part of series. Hope you will find it useful
I am still child in this tech, i am using you r document to complete my cluster installation
thank you so much if i need u r help i will ask u definetly , i think u will not say no to help in this
Thanks for the comment. Feel free to ask question on this blog and I will reply to them as soon as possible.
ALl I can say is youve given me something to do over the weekend and Im thankful for it!
Thanks for sharing your knowledge mate.
I am happy to hear that you would be using my blog to learn something new and help your business grow.
In case, you feel you need help please feel free to comment and I will reply them ASAP (unless I am not sleeping)
part 5 step 1 mentions log off node2. When should this node be re-started and re-logged on?
Excellent article and well worth the study.
Thanks for the feedback.
This step is required as work around of issue mentioned in KB.
Once SQL Setup is complete, you can log back in.
Did I answer your question?
Thank you very much for guide.
Really an EYE Opener for me regarding the virtual HD stuff as it eliminates the third party iSCSI Target software.
Nice article, I've tried it on my virtual server. The system Configuration Check is success , but in the last part I always got an errors when tried to install SQL 2005,
Microsoft SQL Server 2005 9.00.1399.06
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service PACk 2 (Build 3790)
Time : Mon Feb 2009
SQLNODE1 : The current system does not meet the minimum hardware requirements for
this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.
Task did not appear to start on machine: \\SQLNODE2
My cluster admin just doing fine, both of node bring online.
JFYI my VS node spec is:
- Shared disk : 16 GB for system (C), 3 GB for Data (X), 512 MB for Quorum(Q) and 512 MB for MSDTC (M)
Do you have any suggestion?
As per error it looks like you are running setup from SQLNode1. So few things to check..
1. If you are running setup from CD disk (ISO Image), make sure that you able to access \\SQLNODE1 from SQLNODE2 and the setup files share. It would be better if you can copy the setup files on C drive and then run the setup.
2. Make sure all sessions are logged off from SQLNODE2. There is a bug in SQL Setup which will cause setup to fail if you have any session open on remote node. http://support.microsoft.com/kb/910851/en-us
Let me know if it does not help.
Thanks, that's a good idea, I've tried to copy source CD to C: and running setup smoothly till finish :)
A few to ask, after setup finish if i opened the SQLNODE2 i can't find the shared disk (Q , M or I), from device management i found unknown/unreadable for 3 shared disk except C: . Is that a normal condition?
And how to test SQLNODE1 fail over to SQLNODE2?
Many thanks for the answer.
That's the behaviour of cluster (share nothing model). Disk would be visible to the node which owns the disk.
To test failover, you can open cluster Administrator (start>run>cluadmin) and do "Right click, Move Group" on SQL Group to check failover.
Such a beautiful article, what a beautiful explanation, WOW. Nice job balmukund keep it up.