Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Database mirroring question Expand / Collapse
Author
Message
Posted Thursday, January 31, 2013 1:05 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, April 8, 2014 8:50 AM
Points: 27, Visits: 74
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,

Post #1414302
Posted Thursday, January 31, 2013 1:20 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 7:55 AM
Points: 42,478, Visits: 35,545
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1414309
Posted Thursday, January 31, 2013 1:34 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, April 8, 2014 8:50 AM
Points: 27, Visits: 74
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 ?
Post #1414318
Posted Friday, February 1, 2013 1:36 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 7:55 AM
Points: 42,478, Visits: 35,545
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1414487
Posted Monday, March 11, 2013 10:20 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 5:28 AM
Points: 102, Visits: 1,050
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
Post #1429378
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse