Re: SQL Server Clustering - OS(64-Bit) SQL (32-Bit)

Tech-Archive recommends: Fix windows errors by optimizing your registry

SQL 2000 is supported on a 64-bit platform (AMD or EM64T only, no Itanium)
with SP4 and higher. This applies on a cluster as well as a stand-alone
system, so the answer to your first question is yes, it can be set up that
way.

As for the migration from SQL 2000 to SQL 2005 64-bit, that is not too much
trouble. You cannot do an in-place upgrade because of the 32 to 64 bit
difference, but you can install a second SQL instance using SQL 2005 on the
cluster. You can then detach the databases from the 2000 instance and
reattach them to the 2005 instance. If downtime is more important and you
have disk space, you can log ship from the 2000 instance to the 2005
instance and perform a cutover in less than 15 minutes, provided you have
tested everything, including security and client access.

The real key here is not the 32 to 64 bit conversion, it is testing the
side-by-side migration from 2000 to 2005. A well-planned and well-tested
changeover can go smoothly and quickly. Anything else is very risky.

Note that I am not trolling for work, I have all I can do, but you might
look at renting a cluster migration expert to assist with this project.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




"Kamal Hassan" <KamalHassan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2609214B-CD0E-4F68-AC1D-CD49B7FC5815@xxxxxxxxxxxxxxxx
Currently we have 4-NODE SQL Cluster as follows:

H/W = 32-Bit processors
Windows 2003 EE (32-Bit)
SQL 2000 EE (32-Bit)

We plan to setup a new 4-NODE SQL Server Cluster with the intention to
upgrade to SQL 2005 64-Bit later.

Phase I

Set up 4-NODE SQL Cluster with following h/w & s/w configuration:

H/W = 64-Bit
Windows 2003 EE (64-Bit)
SQL Server 2000 EE (32-Bit)

Phase II

Upgrade SQL Cluster to SQL 2005 EE (64-Bit)

Here is my question;

a) Is it OK/feasible to setup/configure the 4-NODE SQL Cluster as per
Phase I

b) If YES then would it be possible/practical to upgrade to SQL 2005 as
per
Phase II and what would be the steps for MIGRATION/upgrade with MINIMUM
down
time?

Let me know if I should call/contact Microsoft to confirm the above
setup/configuration?

Thank you!



.

Relevant Pages

  • Re: SQL 2005 Upgrade
    ... introduce SQL 2000 into the cluster? ... or version upgrade transparently during the install. ... The Microsoft SQL Server support policy for Microsoft Clustering ...
    (microsoft.public.sqlserver.clustering)
  • Re: Issues creating a new failover cluster on the same server
    ... G:\Microsoft SQL Server\MSSQL.1 ... CHNSQL04 Cluster Group ... Drives: H and F ... Group, the MS DTC Group, and each of the SQL Server Instance Groups running ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Newbie - SAN Advice
    ... Senior SQL Infrastructure Consultant ... SAN/Smart array or through a fibre channel switch. ... The SAN or Smart array will dictate what internal connection the disks ... single-instance cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Question
    ... You could make a test environnement through Virtual Machine to get a picture on Cluster. ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: SQL server 2005 SP2 failing on cluster
    ... We have been told for a long time that MSDTC is optional on a cluster but is all but required in the real world. ... I'm having problem to update my SQL cluster with SQL server 2005 SP2. ... Package Platform: x86 ... see Help and Support Center at ...
    (microsoft.public.sqlserver.clustering)