Alias in the DNS.

Hi,
I have two different server with the same SQL instance
with the same databases on
SERVER1\NODE1 and SERVER2\NODE1, the goal is to be able
to switch from SERVER1 to SERVER2 without causing users
problems.
We thought to add in the DNS server the IP adresses of
the server1 and giving the TEST ...but that's not work
because the ip adress alone is not realy associate with
the SQL Instance. And we can't put in DSN an IP adress
with the \NODE1.
So, someone can help me to put on this full system
availability strategy ?
Thanks...
The client software can specify the IP address and instance name
instead of the computer name and instance name. Ex:
192.x.x.x\<ABCInstance>.
Lou Arnold
Ottawa.
On Thu, 22 Jul 2004 06:29:12 -0700, "Pierre"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I have two different server with the same SQL instance
>with the same databases on
>SERVER1\NODE1 and SERVER2\NODE1, the goal is to be able
>to switch from SERVER1 to SERVER2 without causing users
>problems.
>We thought to add in the DNS server the IP adresses of
>the server1 and giving the TEST ...but that's not work
>because the ip adress alone is not realy associate with
>the SQL Instance. And we can't put in DSN an IP adress
>with the \NODE1.
>So, someone can help me to put on this full system
>availability strategy ?
>Thanks...
|||Yes i know that Lou but it's not our goal to past all the
300 user's computers to change the client network alias
ip adresse.
We use actualy an alias name for a server with a default
installation of SQL Server .. and that's work good on
because the ip adress in the DNS is the same name than
the SQL Server name. And we can easyly change the ip
adress into the DNS Server and we don't have to change
300 odbc connections...

>--Original Message--
>The client software can specify the IP address and
instance name[vbcol=seagreen]
>instead of the computer name and instance name. Ex:
>192.x.x.x\<ABCInstance>.
>Lou Arnold
>Ottawa.
>On Thu, 22 Jul 2004 06:29:12 -0700, "Pierre"
><anonymous@.discussions.microsoft.com> wrote:
with
>.
>
|||Ok. You're right. Sorry I can't help further.
Lou.
On Thu, 22 Jul 2004 11:03:25 -0700,
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Yes i know that Lou but it's not our goal to past all the
>300 user's computers to change the client network alias
>ip adresse.
>We use actualy an alias name for a server with a default
>installation of SQL Server .. and that's work good on
>because the ip adress in the DNS is the same name than
>the SQL Server name. And we can easyly change the ip
>adress into the DNS Server and we don't have to change
>300 odbc connections...
>instance name
>with
|||Hi Pierre,
Are the instances in your example on a SQL Cluster or StandAlone?
Are you using 1433 as the port or other?
When your clients connect to the Server do the specify Server\InstancName
or just Server?
The reason I ask is that MDAC has some rules in connections to Named
Instances.
You must use either :
1. Server\InstanceName
or
2. Server, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin,
That's a standalone servers. and actually the clients are
using SERVER1\NODE1 ( port:1435 ) ... and I want to be
able to switch easily to SERVER2\NODE1 ( port:1435 ).
Actually we use an alias in th DNS for a SQL Server (
just server like you wrote ) and that's work very well
because ... the ODBC's client are configured with an
alias named ALIAS1 whose got the SERVER1 IP Adress in the
DNS ... When we want to switch, we just change the IP
Adress of the alias ALIAS1 in DNS and that's it ... the
clients use the SERVER2 without causing connectivity
problem ...
But with Instancename we can't use this strategy but we
would like because we think it's a good way to keep alive
an application 24 hours a days ...
Thanks Again ..
>--Original Message--
>Hi Pierre,
>Are the instances in your example on a SQL Cluster or
StandAlone?
>Are you using 1433 as the port or other?
>When your clients connect to the Server do the specify
Server\InstancName
>or just Server?
>The reason I ask is that MDAC has some rules in
connections to Named
>Instances.
>You must use either :
> 1. Server\InstanceName
> or
> 2. Server, port
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||OK. So, if the client has an alias configure to use Server1,1435 (Using
the SQL Client Network Util) then does this scenario work?
I think it will as long as you've created an alias on each client to
reference the Servername and port. Port being an
important factor.
Since DNS knows nothing about ports or instances, this is the only way i
think it will work. Otherwise, the traffic will
default to 1433 and the clients fail to connect.
Let me know if this makes sense.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.