Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


AlwaysOn - use an Availability group listner or just point to the Cluster name


AlwaysOn - use an Availability group listner or just point to the Cluster name

Author
Message
winston Smith
winston Smith
SSC Eights!
SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)

Group: General Forum Members
Points: 973 Visits: 2040
I have MasterDataServices installed on a server and the database is in an AlwaysOn Availability Group.

The MDM front end currently is set up incorrectly and is referencing NodeA (primary node) for its database.
I want to fix this but im unsure if i should:

-point the MDM front end to the cluster name, so it wont matter what server the databsae is on?
-create an Availability Group Listner, which would also decoupple the database referenced from a particular server.


(note im using MDM here, but that could be any website referencing a database that is in an AlwaysOn Availability Group).

Thanks,
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8780 Visits: 16554
winston Smith (5/6/2014)
The always on front end currently is set up incorrectly and is referencing NodeA (primary node) for its database.
I want to fix this but im unsure if i should:

What front end?
Fix what?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
winston Smith
winston Smith
SSC Eights!
SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)

Group: General Forum Members
Points: 973 Visits: 2040
crap, typo, meant to say the MDM front end. ive updated the original post.
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8780 Visits: 16554
winston Smith (5/6/2014)
I have MasterDataServices installed on a server and the database is in an AlwaysOn Availability Group.

The MDM front end currently is set up incorrectly and is referencing NodeA (primary node) for its database.
I want to fix this but im unsure if i should:

Pointing the web app at the current Primary instance will produce issues if there is an AlwaysOn group failover.



winston Smith (5/6/2014)
-point the MDM front end to the cluster name, so it wont matter what server the databsae is on?

What cluster name are you referring to?


winston Smith (5/6/2014)

-create an Availability Group Listner, which would also decoupple the database referenced from a particular server.


(note im using MDM here, but that could be any website referencing a database that is in an AlwaysOn Availability Group).

Thanks,

A listener should be used to provide centralised access to the AlwaysOn availability group so that the moving of the primary role does not present any issues.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
winston Smith
winston Smith
SSC Eights!
SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)SSC Eights! (973 reputation)

Group: General Forum Members
Points: 973 Visits: 2040
Pointing the web app at the current Primary instance will produce issues if there is an AlwaysOn group failover.

Yep, thats the crux of the post, i want to resolve this :-)

What cluster name are you referring to?

so there is nodeA & nodeB in the cluster. The cluster name is Clust1. I can open SSMS, type in Clust1 in the connection properties and connect to the cluster. I was wondering if in MDM i should referr to this as the instance name, or if i should create an AG Listener.

A listener should be used to provide centralised access to the AlwaysOn availability group so that the moving of the primary role does not present any issues.

And that answers my last question!

New question, whats the benefit of using the AG Listener over the cluster name? after a node failure and failover, the database should still be accessable by either, right?
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8780 Visits: 16554
winston Smith (5/7/2014)
Yep, thats the crux of the post, i want to resolve this :-)

ok, so create a listener for your AlwaysOn group



winston Smith (5/7/2014)
so there is nodeA & nodeB in the cluster. The cluster name is Clust1. I can open SSMS, type in Clust1 in the connection properties and connect to the cluster. I was wondering if in MDM i should referr to this as the instance name, or if i should create an AG Listener.

You're connecting to the Windows Cluster Client Access Point right?
This is a really bad idea, quite apart from the fact that this CAP is meant for Cluster management access only!!
Create a dedicated listener for your AlwaysOn group.



winston Smith (5/7/2014)
And that answers my last question!

Good, so get cracking then ;-)



winston Smith (5/7/2014)
New question, whats the benefit of using the AG Listener over the cluster name? after a node failure and failover, the database should still be accessable by either, right?

There is no benefit, do not use the Windows Cluster CAP to access the SQL instances, period!

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search