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

Geoff

In my case things get a little complicated (for me) on the storage
area. One of my instances has 140 databases with a total of 600 Gbytes
of data and is spread on 8 LUNS. The other instance has 40 databases
with a total of 500 Gbytes and is spread on 8 LUNS.

To complicate a little more, the LUNS are replicate from the storage on
our main site to another storage on our backup site.

My initial idea was to create a new instance, add two disks to it and
use the mount point to spare the drive letters, configure the LUN
replication and start moving a group of databases each of time.

The main reason to use the upgrade method is because it's more fast
to fall back just a group of databases back than to fall back (restore)
all the databases from the instance. If I make an upgrade in place with
140 databases and one of the systems that access one of the databases
failed I have to fall back the entire instance.
Of course that I am going to test all the systems, in my case more than
100, but something may be forgot by one of the 50 analysts that will be
involved on the tests.

Thanks for you reply.

Geoff N. Hiten wrote:
SQL supports different versions at different revision levels. The tools
will be at the latest rev level, but each instance can have a different
version and service pack level. When you do an upgrade, you do one instance
at a time anyway.

As for the linked server issue, you shouldnt have any huge issues. The
names and logins remain during an upgrade so you shouldn't have any problem.

You don't have to double your storage to do a partial side-by-side
migration. You can install SQL 2005 as a third instance and get it
configured and working. You can then detach the databases from your SQl
2000 instance, migrate the disk resources to the new resource group, set the
dependencies, and attach them to your SQL 2000 instance. Repeat for the
second SQL 2000 instance. You would have to detach and restore to go back,
but you at least have a failback path.

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





"Carlos Selonke" <ce.souza@xxxxxxxxx> wrote in message
news:1167758432.591386.141320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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.


.