Re: SQL 7.0 on Windows 2000

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

  • Security strategy: Access client/SQL Server
    ... I will be creating an application using MS Access as a client to SQL ... SQL Server resides. ... permissions for group X to open form A, users would need to get a new ...
    (comp.databases.ms-access)
  • RE: Failed upgrade to SCCM
    ... When you only see 2 actions, that generally means that the client cannot ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ... SQL Server security mode and as we require the SQL server to be in SQL & ... however fails at "Install SMS provider components". ...
    (microsoft.public.sms.setup)
  • SQL and Bandwidth use
    ... Dell PowerEdge server, Dual Xeon 2.4GHz processors, 4 GB ... Run Query against database, in Great Plains Client ... bandwidth usage by ... Client PC is on same segment as SQL server (not passing ...
    (microsoft.public.sqlserver.connect)
  • RE: Monolith -> layered client/server?
    ... That way you can put as many logical layers (data access, business rules, ... whatever) on a server talking to your SQL Server... ... Client would require db connection info. Using a windows app on the ... > to a layered .NET SQL server version. ...
    (microsoft.public.dotnet.general)
  • Re: error setting up ODBC for remote sqlexpress database
    ... We were able to get it to work with the ODBC native client driver. ... Server could be stopped in the client. ... is to install Management Studio for SQL Server 2005 Express ...
    (microsoft.public.sqlserver.odbc)
Loading