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

Creating 2 AlwaysOn clusters for 1 app Expand / Collapse
Author
Message
Posted Friday, April 11, 2014 11:43 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, April 12, 2014 6:46 AM
Points: 1, Visits: 5
We have 2 SQL 2012 servers. Our application has 2 databases. We are creating an AlwaysOn cluster. Is it good to create 2 AlwaysOn clusters to have 1 database primary on one of the servers and the other database primary on the other server?

I have been asked if it is possible to have one database running on one server and the other database on the other server. Is this possible without creating 2 separate AlwaysOn clusters? Is it a good idea to do this?
Post #1561085
Posted Friday, April 11, 2014 12:27 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 5:39 AM
Points: 4,463, Visits: 6,391
Bsthomas0327 (4/11/2014)
We have 2 SQL 2012 servers. Our application has 2 databases. We are creating an AlwaysOn cluster. Is it good to create 2 AlwaysOn clusters to have 1 database primary on one of the servers and the other database primary on the other server?

I have been asked if it is possible to have one database running on one server and the other database on the other server. Is this possible without creating 2 separate AlwaysOn clusters? Is it a good idea to do this?


If there is any interplay between the two databases I would STRONGLY encourage you to keep them on the same server and in a single AG. Linked servers SUCK in SO many ways.

Outside of that if you want them to be split then you need 2 AGs. I have done this for clients and there is no issues (that aren't already in play with AGs).

Don't forget that there are a WIDE array of things you need to do when you have AGs, like SID-coherent logins, SQL Agent Jobs, how to (re)point various constructs if/when a failover occurs, etc.


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1561101
Posted Friday, April 11, 2014 7:31 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 10:21 AM
Points: 6,737, Visits: 14,369
I think what you're asking is can you 2 separate Availability groups. Yes you can. What are you trying to achieve though?

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

"Ya can't make an omelette without breaking just a few eggs"
Post #1561163
Posted Saturday, April 12, 2014 5:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, April 12, 2014 6:46 AM
Points: 1, Visits: 5
We are trying to spread the load across the 2 servers. We do not want to used linked servers, so 2 AlwaysOn clusters is out. It is not a big deal if we cannot. I was just asked if it was an option.
Post #1561185
Posted Monday, April 14, 2014 11:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, November 4, 2014 8:46 AM
Points: 2, Visits: 9
Then simply create two avaliablity groups and add each database to it's own avaliablity group. Then make each of the avaliabliy groups (and in turn each database) primary on it's own server. You are going to have to fiddle with your backup process/routines however, but nothing a little reseach into sql server backup copy only will not solve.
/Colin
Post #1561606
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse