Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 High Availability (2008)
 failover to mirrored server - machine name?

Author  Topic 

notshai
Starting Member

8 Posts

Posted - 2011-07-05 : 09:42:43
i am working on a 2005 to 2008 sql R2 migration.
i would like to use simple mirroring (without witness server).

one of the issues i am having is with the SSIS packages which refer (hard coded) to machine name "DB1" - what happens in a scenario where the primary DB server goes down and i want the mirrored server to take over?
the SSIS' will look for the name "DB1" which isnt available. the mirrored server is named "DB2".

during such a scenario, would i need to rename "DB2" to "DB1" ?
i read some articles about changing machine name and it doesn't look a seamless process.

when the primary server is fixed, how do i go back to the original name?

thank you

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2011-07-05 : 16:49:56
I see a couple of options:

1) Make sure your connections are using the latest version, and specify the partner/failover server. This should work so the packages will attempt to connect to the other server if the partner is down.

2) Use a configuration file to specify the connection information. This would allow you to specify on each server the specific connection information needed to run the package.

Jeff
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-07-05 : 20:31:28
3) Use a DNS alias.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2011-07-06 : 03:12:44
quote:
3) Use a DNS alias.
Just to elaborate on Taras suggestion: this is done through SQL Server Configuration Manager under SQL Native Client Configuration -> Aliases. Name your alias "PrincipalDB" or something, use port 1433 as portnumber (unless you've changed it), TCP/IP as protocol and add the IP/name of the active database in Server.

- Lumbago
My blog-> http://thefirstsql.com/2011/02/07/regular-expressions-advanced-string-matching-and-new-split-function-sql-server-2008-r2/
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-07-06 : 16:04:28
Actually no that's now what I meant.

I mean an alias in your DNS server.

What you've shown is a client-side alias. I don't like them for situations like this as that client-side alias needs to be on each of your clients, whether they be desktops or app/web servers. A DNS alias does not require this, it's on the DNS server side and broadcasts throughout your network.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Lumbago
Norsk Yak Master

3271 Posts

Posted - 2011-07-07 : 02:27:21
Oh, sorry for putting the wrong words in to your mouth Tara :) I agree that changing the DNS is a better solution IF you have control over the DNS or you are good friends with the people that manage your DNS. In my world that's rarely the case as doing changes in the DNS usually involves quite a bit of bureaucracy.

- Lumbago
My blog-> http://thefirstsql.com/2011/02/07/regular-expressions-advanced-string-matching-and-new-split-function-sql-server-2008-r2/
Go to Top of Page

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2011-07-07 : 23:34:16
The problem with using a DNS alias is that you have to make the change manually. There is no automatic setup that will determine that your principal is down and change the entry to the mirror.

Using either the native client configuration and specifying the partner, or using package configuration on each system to identify the connection information does not require any manual intervention.
Go to Top of Page
   

- Advertisement -