January 31, 2013 at 1:05 pm
Hi,
We use database mirroring in sql server 2008 r2.
We have 1 primary server and 1 mirror server.
Our application connect to the primary instance with ip address.
If our primary server is down and we failover to the mirror server, Our application will not be able to connect.
Our plan is to put the ip address of the old primary server to the mirror (new primary).
BUT, Does changing the ip address will confuse the database mirroring setting ?
Can we do that if we think about the endpoint config ?
regards,
January 31, 2013 at 1:20 pm
Read up on "Transparent Client Redirect". If you're using ADO.net or SNAC to connect, you don't need to do any of what you're suggesting.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 31, 2013 at 1:34 pm
Okay, but if we do not use ADO or SNAC, can we change the ip address of the mirror wihtout confuse the database mirroring or should we instead change the connectivity on the application side ?
February 1, 2013 at 1:36 am
No, don't mess with the IP on the mirror.
Read up on transparent client redirect first. You could also give the app both server's names to try, or do a DNS change when there's a failover.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 11, 2013 at 10:20 am
In Database mirroring ,mirror server name should be specified in two modes.
1.Implicit mode
No need to specify failover partner here.By the use of SQL provider ,failover will done with mirror server identification from the memory cache,
2.Explicit mode
We need to specify failover partner in the connection string.
Failover Partner=<servername>” (where <servername> is the name of your mirror server).
Regards,
Kumar
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply