Mirror Partner and Fully Qualified Domain

• Jason Bunn

  SSCommitted

  Points: 1713

  More actions

  April 24, 2015 at 2:39 pm

  #303364

  Hello,

  When we set up mirroring, we can see a fully qualified entry for mirror_partner_name in sys.database_mirroring: TCP://SERVER.DOMAINX:PORT

  However, the column mirroring_partner_instance just has SERVER, without the fully qualified domain.

  This has caused problems when the client is in DOMAINY and the database servers are in DOMAINX. Upon failover, the client is looking for SERVER2.DOMAINY since the client is in DOMAINY, and it fails since the mirror server is SERVER2.DOMAINX.

  The failoverPartner parameter doesn't help, since it isn't used if there is a successful connection to the primary server when the client starts up.

  While we can work around this with hard coding of DNS suffixes on the client, does anyone know if there is a way for the fully qualified domain name to be stored in sys.database_mirroring, mirroring_partner_instance, and thus used for failover?

  Thanks!