John Darby
asked on
Timeout an application seeking remote SQL and redirect to another remote SQL?
I have a BizTalk 2006 R2 Cluster, using a remote SQL Cluster for the back-end. For our Disaster Recovery plan, I have an offsite Standalone cold standby BizTalk server which I want to behave in a specific way...
When this Standalone box is started, I want it to seek the primary SQL Cluster, but if 30 seconds pass without contact, it will attempt to connect to a secondary SQL server. Have you done this before and is there easier way to set this kind of failover in-place?
Thank you!
JohnD
When this Standalone box is started, I want it to seek the primary SQL Cluster, but if 30 seconds pass without contact, it will attempt to connect to a secondary SQL server. Have you done this before and is there easier way to set this kind of failover in-place?
Thank you!
JohnD
ASKER
The BizTalk box will be using the SQL 2005 tools and connecting to either a SQL cluster back-end or a standalone SQL box (both 2005). The crux of the question is if there is a way to have a 30 second timeout seeking one SQL source and opting to seek another (equivalent) SQL source?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to work around this issue at the routing level. Thanks!
what cluster do you have - A\P A\A?
--Usually, all idea of cluster server - apps is using 'virtual' name not sql servers node names; so you do need just specify the name and cluster will takes care the rest ..