Re: SQL 7.0 on Windows 2000
- From: "Geoff N. Hiten" <sqlcraftsman@xxxxxxxxx>
- Date: Thu, 31 Mar 2005 09:04:39 -0500
I wouldn't even try and give them the same names. I would use a DNS srv
record to repoint the old name to the new system (assuming an AD
infrastructure). This has the advantage that you can turn it off and on at
will to test. If you have only one or two client app servers, you can do
the same thing with a client network alias.
Geoff N. Hiten
Microsoft SQL Server MVP
"Thom" <Thom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3FB92A5-3D23-42BE-94FA-9F23ECB5C44B@xxxxxxxxxxxxxxxx
> Okay go ahead and shred me now, and then please see if you can answer my
> question. I have a client that is living in the dark ages. Currently they
> are
> clustered on NT4.0 and SQL 7.0 using legato. We are moving them a step at
> a
> time to SQL 2000/Windows 2003 clustering. W2k and SQL7.0 using microsoft
> clustering is the first baby step. I need to know if I can name my SQL7.0
> virtual server the same as the cluster.
> We are trying to have minimal impact on the apps, that hit the server and
> they are not sure if any is mapping to the cluster at this time.
.
- Follow-Ups:
- Re: SQL 7.0 on Windows 2000
- From: Thom
- Re: SQL 7.0 on Windows 2000
- References:
- SQL 7.0 on Windows 2000
- From: Thom
- SQL 7.0 on Windows 2000
- Prev by Date: Re: Defunct Drives Issue
- Next by Date: RE: SQL stopped because spid3
- Previous by thread: SQL 7.0 on Windows 2000
- Next by thread: Re: SQL 7.0 on Windows 2000
- Index(es):
Relevant Pages
|