Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
 Posted - 2006-04-18 : 22:37:28
|
| I just installed my first SQL2K5 clustered instance today. I ran into a few problems, and just wanted to post my impressions.First, one big difference with the cluster install is that you will have to get your AD admins to create up to 4 domain groups that you can administer. We have a standard domain user called SQLSERVICE that we run our SQL Servers under. In our scenario we created the 4 groups (SQL2K5_SERVER, SQL2K5_AGENT, etc.) and granted the SQLSERVICE account the ability to manage these groups. So far so good.Now on to the gripes. At the screen where you type in the IP address for your virtual host you can no longer advance to the next octet by hitting the '.' (dot) key. THis is annoying.2nd, problem we ran into was it turned out that our SQLSERVICE account also had to be a member of the 4 new domain groups we created, not just have the ability to manage those groups. I didn't see this in the documentation, but it was probably an oversight. I spent a half hour or so figuring this out.3rd problem, when the cluster install fails due to the above issue (maybe for other reasons to, not sure at this point) the setup fails to remove scheduled tasks that have been scheduled to run on the remote node. THis is bad, because even when you fix the 2nd issue above, your installations will continue to fail until you remove the previously scheduled scheduled tasks.Lastly, not really a problem but the installation logs are no longer in the same location as before. I got too lazy to read the docs to find them so I had to dig around. THis is just a minor inconvenience, but now they are located (in my case) in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files. You also need to look at the scheduled tasks log to troubleshoot problems on the remote nodes (which is totally new). Nice thing with this setup is that now almost all the logs needed to troubleshoot a problem are in one place - I just couldn't find that one place initially. So this is really a good thing..-ec |
|
|
|
|
|
|
|
SQL2K5 cluster installation first impressions