Re: SQL 7.0 on Windows 2000

Sorry for the confusion... sql will not be using the file shares. but
individuals may be using them... ie. copy some data over to the windows
share and then use dts to load the data.

So with legato, and I don't know much about it, the user would map a drive
to \\servername\d_drive and then copy it over. since it was a default
instance the sql had the same name as the server.

Now with MSCS we have a two physical servers, nodea and nodeb, the get
clustered and given the name of the old server <servername> from above. The
user would map drive to \\servername\d_drive and copy the file as before.

But now I have virtual sql that doesn't have the same name as before
<servername> from above. Since the customer isn't sure about the use of the
file shares I would like to be able to have people still connect to sql
server using <servername> as before with legato. but I have already used
that name for the windows cluster name.

That is my true dilemna, will this work using DNS and pointing the old
server name and port 1433 to the new sql virtual name?

Thanks for the assitance Geoff.

"Geoff N. Hiten" wrote:

> 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: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now successfully installed them. ... Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC. ... We are trying to install the client software. ... We understand that a Northwind training database is available for SQL Server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: TDS vs. TCP
    ... I start capturing the network traffic between SQL ... Server and the client. ... I don't see any TDS packets but the communication between SQL ... stand-a-lone server and the client, ...
    (microsoft.public.sqlserver.clustering)
  • Re: DMX Query response time
    ... the prediction is done in client-side. ... In SQL 2005, all predictions are performed in the server. ... >>>> server are remoted to the client and cached into client memory until ...
    (microsoft.public.sqlserver.datamining)
Loading