Re: SQL 7.0 on Windows 2000

File shares and SQL Server services are two different issues. You can alias
a SQL server many ways, including DNS records and Client aliases. Resolving
share names is a different issue. A SQL Server 2000 system normally doesn't
use file shares, except in replication snapshot resolution. Also, the SRV
record includes a service name and an IP address and a port number.
Normally, these records are registered by the service so other systems can
find it. This is how AD finds its various management roles "under the
covers".

GNH


"Thom" <Thom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A4AA339C-5740-4481-86D6-CD048F459E74@xxxxxxxxxxxxxxxx
> Okay, just for a little clarification for myself,
> We are in AD so if this was the setup:
> physical01
> physical02 - both clusteres to virtual03 ip of 192.168.0.1 (example only)
> sqlvirtual04 ip of 192.168.0.2,1433 (example only)
>
> If i went into DNS and setup a record to point 192.168.0.1 to sqlvirtual04
> then the shares could be mapped as \\sqlvirtual04\d_drive
> and sql would still be registered as sqlvirtual04?
>
> Let me know if this is what you were referring to?
> Since the client doesn't know if the shares were being used on the
> original
> sql server, I would like to leave name the virtual sql the same as the
> original, but allow drives to be mapped also.
>
> "Geoff N. Hiten" wrote:
>
>> 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.
>>
>>
>>


.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL and DNS
    ... cliconfig.exe is already on the client machine, with MDAC. ... Tibor Karaszi, SQL Server MVP ... In a pure DNS ...
    (microsoft.public.sqlserver.server)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)