Hi All SQL Gurus
Here is my scenerio
I have a Win2003 SQL Server 2000 Cluster server.
Now the plan is to upgrade to SQL2005 But they do not want to upgrade the
existing instance. what the client wants to do is install another instance
of SQL 2005 on the same virtual server.
here is my problem.
1>Can i install named instance with different port # in the same cluster
group. say group 1. or do i need another sql group with another ip, disk and
n/w name.
2> if i move the disk between the groups. let us say i create another group
for this new sql 2k5 instance called Group2005, and want to move the disk
resources from original group Group2000 to new group2005, will the data on
the group be deleted.?
Because the size of the database is 5 TB, backup and restore is not an
option., so i was thinking of installing sql 2005 as another instance and
just attach the databases..

Will this work..
thx

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote

1. No. One instance per group.

2. You can move disks between groups. The data on the disks stays intact.

I would create a new instance, synch the logins, Stop both instances, change
the groups, fix the dependencies, start the new instance, and attach the
databases.

If you can, snapshot the data files before moving them to the new instance.
Once you attach the data files to the new instance, you cannot put them back
on the old one.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jason" <bornscorpio30 (AT) yahoo (DOT) com> wrote