Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Availability Group Cluster Name always connecting to a specific server rather than the primary node

$
0
0

Hi
I am hoping someone can help me,

I have a SQL Server 2012 Always On Availability Group

Server 1 - SQL Server 1
Server 2 - SQL Server 2
SQL Cluster name - CLR
Availability Group Name - AG 

I have some application that uses databases that is residing in Availability Group AG.

When the AG is hosted by Server 1, Server 1 is my Primary & Server 2 is my Secondary
When I failover the AG, Server 1 becomes secondary, Server 2 becomes primary Node

The problem is, My Application connects to databases using the cluster name CLR. I notice that CLR always connects to Server 1. so, if my AG is hosted from Server 2 , that means because my CLR connects to server 1, the database becomes read only.

is this the design of SQL 2012 always availability group?

What I need is, if I connect to cluster name CLR, the connection to the Availability Group should point me to the server that is holding the Primary Node.

Alternatively, if the cluster name CLR will always connect to Server 1 then I need to make server 1 read-write capable so my application can write to it. I have selected the availability group properties and changed the secondary to read-write, but that doesn't fix my problem.

Can someone point me to the right direction please?

Thanks in advance.


MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation



Viewing all articles
Browse latest Browse all 4689

Trending Articles