[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 233
  • Last Modified:

SQL 2000 to SQL 2008 - Clustering and disk system questions

We have an existing SAN connected 2000 SQL cluster running on Server 2003, we're now looking moving to Server 2008 and SQL 2008 in order to take advantage of some of the newer SQL capabilities (the software the company uses gets some added functionality that we're interested in).

Since we have relatively new servers, we're looking to do this without adding any new servers.  I do have the same exact disk system available on the SAN, so I can match number of spindles and disk setup.

My idea was to evict Node 2 from the existing cluster, wipe and rebuild it with Sever 2008 and SQL 2008.

My questions are:

1.  If my current SQL 2000 disk setup is working, is it sufficient to mirror it for SQL 2008?  (I have 4 drives mirrored for data, 2 drives mirrored for logs, 2 drives mirrored for TempDB, and 2 drives mirrored for Master and Quorum).
a.  I read that TempDB is used more in 2008, but I don't have a sense of how much more

2.  Can I build a standalone cluster server and then convert it to a cluster?  Can I build it as a cluster with only 1 node and add a 2nd note later?
  • 3
1 Solution
I think your basic idea is fine.
Evict one node and reimage it as Server 2008, build a new one node Microsoft Windows Cluster. Install SQL Server 2008 as a clustered instance.
Migrate/upgrade your databases
Reimage the 2nd machine and join it to the new cluster.

Basic performance considerations for tempdb continue to apply. Try to put tempdb on its own separate fast disk. Assuming your Servers are multiprocessor, set up temp db to have as many data files as there are processors (or cores). For example, on my 2cpu quadcore server, I have 8  datafiles making up tempdb.
ITDharamAuthor Commented:
Thank you pettmans, I'm hoping to get a couple more responses for confirmation.
ITDharamAuthor Commented:
Looks like no one else is interested...that's ok.

Another question, I'll want to keep the same SQL server name.  Can I build the new cluster using server-temp and then rename once I'm ready to switch?  I remember running into some kind of problem when I did this for SQL2000, but I don't remember exactly what the problem was.
ITDharamAuthor Commented:
I was hoping for some more hits but it seems that it wasn't meant to be.  Seems like you win!!  Thanks for the help.

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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