Diverting clinet network traffic form primary server to secondary server in case of log shipping

Question

Diverting clinet network traffic form primary server to secondary server in case of log shipping

anoop.mig29

SSCrazy

Points: 2035
More actions
July 23, 2012 at 11:40 pm

#276574

hi we are trying to carry out log shipping in sql server 2008 enterprise edition.problem is how to divert client traffic form primary server to secondary server once we want to use secondary server i.e when secondary server comes online. is there some command or some particular tool to divert client traffic to secondary server .
also is possible to do log shipping from 2005 to 2008 and vice versa
Thanks
Anoop

Perry Whittle SSC Guru Points: 233792 More actions · Answer 1

anoop.mig29 (7/23/2012)
hi we are trying to carry out log shipping in sql server 2008 enterprise edition.problem is how to divert client traffic form primary server to secondary server once we want to use secondary server i.e when secondary server comes online. is there some command or some particular tool to divert client traffic to secondary server .

The use of alias's would be the most obvious option

anoop.mig29 (7/23/2012)
also is possible to do log shipping from 2005 to 2008 and vice versa
Thanks
Anoop

you can log ship from 2005 to 2008 but once you bring the secondary database online the log ship scenario is broken and would require completely restarting

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQL Show SSCertifiable Points: 6143 More actions · Answer 2

Log shipping will not work from 2008 to 2005 as backup files are not backward compatible.

anoop.mig29 SSCrazy Points: 2035 More actions · Answer 3

The use of alias's would be the most obvious option

thanks for your reply but can u elaborate more / or can u tell procedure

thanking You

Anoop

DBA328 Hall of Fame Points: 3952 More actions · Answer 4

Suppose you use webserver connecting to DB Server.

Then you could create alias on Webserver and using it in DB connection string(SQL Server Configuration Manager->SQL Native Client->Aliases).

After the primary server down, you just only change the DB Server name to a secondery server, then the application could direct to the correct server.

anoop.mig29 SSCrazy Points: 2035 More actions · Answer 5

DBA328 (7/24/2012)
Suppose you use webserver connecting to DB Server.
Then you could create alias on Webserver and using it in DB connection string(SQL Server Configuration Manager->SQL Native Client->Aliases).
After the primary server down, you just only change the DB Server name to a secondery server, then the application could direct to the correct server.

thanks DBA328 for reply