SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Setting up multiple AG's on 1 server


Setting up multiple AG's on 1 server

Author
Message
e90fleet
e90fleet
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 1001
Hi all, question for you please:

i am upgrading sql from 2008 to 2012 and on one instance we have 3 databases setup with mirroring.
The plan is to use AAG but i am not sure if i need to create one availabilty group with 3 databases or i can create 3 separate availabilty groups with 1 database in each availability group.
What will be disadvantages/advantages with creating 3 separate availabilty groups with 1 database in each availability group? how about performance and
server resources? it is used more resources when you have more AG's on the instance opposed to just 1?
This AG will be setup as synchronous with auto failover.

The reason why i am thinking to setup 3 separate availabilty groups with 1 database in each availability group is because
if for some reason the database is not in synchronous mode i can easily remove replica until the problem is solved for just 1 database instead of 3.
SQLSACT
SQLSACT
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4912 Visits: 2969
e90fleet (9/20/2013)
Hi all, question for you please:

i am upgrading sql from 2008 to 2012 and on one instance we have 3 databases setup with mirroring.
The plan is to use AAG but i am not sure if i need to create one availabilty group with 3 databases or i can create 3 separate availabilty groups with 1 database in each availability group.
What will be disadvantages/advantages with creating 3 separate availabilty groups with 1 database in each availability group? how about performance and
server resources? it is used more resources when you have more AG's on the instance opposed to just 1?
This AG will be setup as synchronous with auto failover.

The reason why i am thinking to setup 3 separate availabilty groups with 1 database in each availability group is because
if for some reason the database is not in synchronous mode i can easily remove replica until the problem is solved for just 1 database instead of 3.


I am not sure if I need to create one availability group with 3 databases or i can create 3 separate availability groups with 1 database in each availability group


Both configurations will work

As far as performance goes, I haven't tested this enough to determine with setup is best.
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