November 11, 2008 at 4:31 pm
Our 3 databases of size 70 to 100 gig are running on Standalone server.
There is transcational replication going on for one database.
SQL server is 2000 SP4.
Now we want to convert this standalone server to 2 node cluster.
How to do that and what parameters need to consider?
what will be the minimum downtime?
November 11, 2008 at 8:17 pm
My advice:
Forget building a cluster out of a standalone.
Build the new 2 node cluster and make it SQL 2005 (since you posted in the 2005 forum). Set up your maintenance routines and monitoring, run some tests then migrate your existing databases to the cluster, making sure to kill the replication on the old server and recreate the publication/articles/subscription using the new clustered instance.
Migrating databases is easy using the backup and restore method... just capture the old server's logins with microsoft's sp_helprevlogin stored procedure and recreate them on the new node.... don't forget to fix any orphan db users after you restore the SQL 2000 backup to the 2005 server with sp_change_users_login, and set the DB to compatibility level 90. Run a dbcc checkdb, then sp_updatestats on each migrated databases and you should be set as far as DB's are concerned.
Dont' forget to migrate DTS packages or any other server-level agent alerts, or whatever you have going on.
Someone out there might also post about running the Microsoft upgrade advisor before migrating.
Cheers!
~BOT
Craig Outcalt
November 12, 2008 at 8:07 am
no but this will take a lot of time
November 12, 2008 at 10:09 am
You cant make an omelette and all that...
Some other things to consider:
1. I assume you use SQL accounts as its a standalone server, this makes sp_help_revlogin_2000_to_2005 (check out http://support.microsoft.com/kb/246133 METHOD 2) even more important as even if you recreate the account the SID's may not be the same (without proper export) and that will lead to orphaned users and lots of issues.
2. If you do go for a SS2K5 cluster, I wouldn’t bother with the replication. Either go with a standard A/P cluster (if you have ability for shared disk volumes (SAN)) or just forget the cluster and mirror. I wouldn’t attempt a mirror on SS2K, it never worked properly hence the popularity of replication.
3. Not all DTS packages can be ported to run on SS2K5 but either way you will have to install the legacy compatibility tools (simple install).
Ok, so basically we are saying all of this cause SQL Server 2000 is end of life now and strictly speaking no-longer supported by MS or at least it wont be for long. Clustering in 2000 is possible but not simple to set up (I have never done it but have administered it). SQL 2005 streamlines the entire process and along with W2K3 Server makes the whole thin a lot more reliable.
Sorry to be a party poop'er, but you did ask. 😉
What ever you do, make sure to check pre-reqs...
Adam Zacks-------------------------------------------Be Nice, Or Leave
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply