SQL 2012 Availability Group Connectivity


good afternoon,

hope well. have setup sql 2012 on windows server failover cluster, spanning across multiple datacentres. have 2 nodes in each datacentre (dc1 , dc2), , fileshare witness on seperate datacentre (dc3). setup have been able setup alwayson availability group. interesting things i've noticed. created listeners on group have same dns name both subnets of dc's (this keep things simple endusers). can see dns entries created, seems have complete dns flush connect availbilty group following failover (doesnt seem on, customers won't know failover has happened). test both dc's configured synchronous commit, failover automatic. whole dns issues seems little awkward, missing there? assistance appreciated. other queries have span around how little connectivity issue would/could resolved on failover.

kind regards,

you have hit on specific issue availability groups common.  fortunately you, there fix. set multisubnetfailover property "yes" in application connection string.  must on current client library code apply.  may notice ag listener (actually cluster virtual name object) registers ip addresses in dns.  older sql client libraries attempted connect a list of sql servers 1 @ time.  multisubnetfailover="yes", library tries all possible connections in parallel.  first server respond ends other attempts.  should eliminate slowdown , dns flush/refresh requirements.

geoff n. hiten architect microsoft sql server mvp



SQL Server  >  SQL Server High Availability and Disaster Recovery



Comments

Popular posts from this blog

Reindexing

Users List

List of charts