Re: Log shipping Failover.
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Mon, 19 Jun 2006 08:12:24 -0400
No, you can't do this for automatic failover. While it is possible to hard
code this in your application, Microsoft does not recommend you do this as
you should redirect your clients as part of a controlled failover processes.
Have a look at the section entitled Log Shipping and Application Code in
http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part4/c1361.mspx?mfr=true
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Miguel" <sentynel@xxxxxxxxx> wrote in message
news:eU9sPX5kGHA.1276@xxxxxxxxxxxxxxxxxxxxxxx
Hello.
How must I configure SQL Server clients, when a failover occurs between a
primary server and secondary server using Log shipping?
I know that in a Mirroring environment I can configure the SQL provider
with 2 server names. Can I do anything similiar in a Log shipping
environment?
Thanks in advance.
.
- Follow-Ups:
- Re: Log shipping Failover.
- From: Miguel
- Re: Log shipping Failover.
- References:
- Log shipping Failover.
- From: Miguel
- Log shipping Failover.
- Prev by Date: Log shipping Failover.
- Next by Date: Re: Stored Procedure Execution Issue
- Previous by thread: Log shipping Failover.
- Next by thread: Re: Log shipping Failover.
- Index(es):
Relevant Pages
|
