February 17, 2008 at 12:59 pm
We have clustered environment for our sql 2000 production databases, we are planning to upgrade to sql 2005, our network team is suggesting that we need to create another new clustered environment similar to that of production and install sql 2005 in that new environment instead of upgrading the existing production db. Please let us know the best way of upgrading since it being clustered environment. Thanks!
February 17, 2008 at 10:22 pm
Even Microsoft recommends not upgrading. Instead, they recommend building a new cluster then installing 2005. There was an article on MS's site a while back.
February 19, 2008 at 11:05 am
Actually, I've done both (upgrading a cluster in place and moving to a new cluster. Our servers were going off lease so I installed SQL 2005 on the new cluster and had it ready in case something went wrong upgrading the original cluster. The upgrade went fine--I just had to install Management Studio and Integration Services on both nodes of the cluster. Then I set up database mirroring to the new cluster and easily switched servers since the database was so large. I was surprised that it worked out so well.
February 21, 2008 at 2:06 pm
Since upgrading the existing production db to sql 2005 is not recommended, we are planning to install sql 2005 in a new server and then migrate the sql 2000 databases to the new server which has 2005 in it. Instead of having clustering which requires special hardware and since it might get costly to implement, we are thinking of going with database mirroring as it does'nt need any additional hardware and we can achieve whatever we get with clustering. And also since database mirroring has automatic server failover and client failover mechanism, we are seriuosly thinking of using Database Mirroring instead of Clustering when we go to SQL 2005. Please let us know your ideas. Thanks!!!
February 21, 2008 at 2:14 pm
We were thinking of using mirroring instead of clustering for high availability but were unable to because the client application can't use the SQL Native Client to connect. Since this is what does the automatic re-direction, the only other option was for the vendor to write code to do it in the case of a failover (it's a third party application that connects with Borland). I hope it works out for you. 🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply