Since DNS can take time to clear the cache, using DNS as part of a manual
failover process has to be practiced to make sure that the manual fail-over
instructions are correctly followed and have a timely effect. Don't assume
this will work out of the gate.
There is nothing wrong with coding the IP address in the connection string.
This is a quick and efficient way to set up the backup. That said, if you
are planning to change the config file, you could put the name of the backup
db server just as easily.
Remember to set up a mechanism for the data in the backup db to be up to
date with the data in the primary db. search for Log Shipping and SQL
Clustering (two different mechanisms).
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"carion1" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In DNS add a generic host name pointed at the primary server. If the
> primary ever goes down you simply change the IP in DNS to point at the
> back up. You could also use Windows Clustering Service.
>
> --
>
> Derek Davis
> (E-Mail Removed)
>
> "Jason Huang" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>> Will it make it any difference if I replace the 'data source' in the
>> "data source=MyServer;uid=SA;password=MyPwd;database=MyDB"
>> with IP, e.g.,192.168.1.1? Where MyServer's IP is 192.168.1.1.
>> We are thinking if the Primary SQL Server failed, then we just change the
>> BackUP SQL server's IP,
>> (givent that the Primary and BackUP SQL Server are syncronized to some
>> extent),
>> so that our application could come back running real soon.
>> Please give me advise. Many thanks in advance.
>>
>> Jason
>>
>>
>
>
Similar Threads
