Upgrade a multi-instance cluster to SQL 2005 on different dates

Hello

I have a Windows 2003 SP1 IA-64 cluster with four nodes. On this
cluster I have two SQL Server 2000 SP4 IA-64 Virtual Instances
installed and each Virtual SQL Instance runs on each owns node. So
basically I have a four node cluster with two active nodes and two
passive nodes.

I have a goal to upgrade both Virtual SQL Servers from SQL 2000 to SQL
2005. I read about the upgrade/migration process differences and I
decided to go with the upgrade method. My decision to stick with the
upgrade method was mostly based on cost issues because I would need to
double my storage capacity to use the migration process.

To minimize the risk associated with the upgrade process I want to
upgrade each instance on a different date.

And that's where my doubts lie.

First doubt: Is it possible to upgrade each Virtual SQL Server instance
on a different date? Case the answer is yes then I have the next two
doubts.

Second doubt: I have linked servers between the Virtual SQL Server
instances. The configuration is: Virtual SQL Server Instance #1 has a
linked server pointing to Virtual SQL Server Instance #2 and Virtual
SQL Server #2 has a linked server pointing to Virtual SQL Server
Instance #1.
Is this an upgrade issue when I upgrade each instance on a different
date?

Third doubt: I have read only transaction replication between the
Virtual SQL Server instances. The configuration is a little bit more
complex but very easy to understand.

Virtual SQL Server Instance #1 is a Distributor and a Publisher and all
the articles published on Instance #1 use the distributor that is
installed on the Instance #1.
Virtual SQL Server Instance #2 is also a Distributor and a Publisher
and all the articles published on Instance #2 use the distributor that
is installed on the Instance #2.

Virtual SQL Server Instance #1 is a subscriber of the articles
published on Virtual SQL Server Instance #2.
Virtual SQL Server Instance #2 is a subscriber of the articles
published on Virtual SQL Server Instance #1.

I read on BOL that I must have the distributor with a version greater
than the publisher (or at the same version with is my case) and the
subscriber can be within 2 versions of the publisher.

I understood that this is not an upgrade issue for me, but did I
understand it correctly?

Please feel free to advise me on any other upgrade issues when
upgrading a multi-instance cluster on different dates.

Thanks in advance for you help.

.

Relevant Pages

  • Re: Upgrading publishers to 2005 (4 questions) sorry i know this isnt a consulting fourm.
    ... You can also try to use the proc sp_vupgrade_replication to upgrade ... If you upgrade the publisher to 2005, you need to upgrade the distributor ... Server version 7.0 Publisher running can have SQL Server 2005 Subscribers; ...
    (microsoft.public.sqlserver.replication)
  • Re: Windows/SQLvirtual name
    ... Unlike a standalone installation of SQL Server, a virtual SQL Server does ... not rely on the name and ip address of the cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Virtual SQL Server times out.
    ... application and a ASP 3.0 page connecting to the same Virtual SQL Server. ... The Connection String used in the problematic code(with some string ...
    (microsoft.public.sqlserver.clustering)
  • Virtual SQL Server
    ... Can I have another Virtual SQL Server on the existing ... Cluster?. ... Active/Passive two-node Cluster Configuration. ... For example Cluster Name is CLUST1 and VIRTUAL SQL SERVER ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster Virtual Server with two Names/IPs possible?
    ... (How this is done differs from SQL 2000 to SQL ... Assuming your virtual SQL Server name is MYVIRTSQL, ... i will configure a virtual server name and ip for the public client access. ...
    (microsoft.public.sqlserver.clustering)