May 13, 2012 at 9:11 pm
Hi All, I am so confused about configuring connection string when we want to configure db mirroirng or replication. how application will detect that it needs to send the connection to new (failover) server? might be a silly questions for all the gurus out there... please advise
May 14, 2012 at 10:29 am
with replication you have a manual failover action, depending upon your mirror session type this will also be either manual or automatic failover. For sessions using a witness you may leverage the Failover Partner option in the database connection string. This will be dependant upon your connection type (ADO.NET, SQL Native client).
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 14, 2012 at 11:44 am
Perry Whittle (5/14/2012)
with replication you have a manual failover action, depending upon your mirror session type this will also be either manual or automatic failover. For sessions using a witness you may leverage the Failover Partner option in the database connection string. This will be dependant upon your connection type (ADO.NET, SQL Native client).
do you have to have a witness to make use of the Failover Partner option?
Data Source=myServerAddress;Failover Partner=myMirrorServerAddress;Initial Catalog=myDataBase;Integrated Security=True;
i thought that worked without a witness too?
May 14, 2012 at 1:43 pm
Automatic failover is only possible with a witness and high safety mode.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 14, 2012 at 2:39 pm
I know that, But manual failover still changes server names on the app side.
May 19, 2012 at 10:53 am
Correct. Automatic failover is not required to use the Failover Partner attribute in the connection string.
For replication, I recommend using load balancing in front of the replicated servers. This gives you the ability to redirect clients to an alternate server without them being aware. The clients/apps would connect to the DNS virtual name and would not need to know the name of the server they are on.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply