SQL2012--pros n'cons of multiple availability groups vs just one

1)does having multiple AG increase the licensing?
2)if all databases could accommodate the settings alike, and all put in one AG, what could be the disadvantages? (other than all going down at the same time).

thanks.
LVL 5
25112Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
1) Only if you need to upgrade from Standard Edition to Enterprise. If the SQL Server instance is already an Enterprise Edition you won't need to pay more for AG.
2) Apart from going down time at same time you may need more resources to have all databases in same AG. If you can afford it then is OK.
25112Author Commented:
so it will be more costly to keep them all in same AG?

1)what standards do you recommend to determine which databases to group together or how many to group together in one AG?

2)
>>you may need more resources to have all databases in same AG
can you suggest what specific hardware resources  that will increase in the above scenario?
Vitor MontalvãoMSSQL Senior EngineerCommented:
1) Depends on your needs and company policies.
2) This should be decided in each case scenario. I don't think there's a formula. Depends in many variables like database version, size, usage, critical level, ...
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

25112Author Commented:
Vitor, when you said ' you may need more resources to have all databases in same AG', I thought perhaps more hard disk? what are other such elements that will come into play for discussion and decision-making?
Vitor MontalvãoMSSQL Senior EngineerCommented:
Disk, CPU and Memory since they will share these resources.
Also Network if the number of connections is too high.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
25112Author Commented:
OK, thanks.

So basically to summarize, would the below cover all aspects of the ‘pro/con’ equation. Would there be any other misc points?

Pros will be:
When an AG goes down, it does not slow down or interfere with all other AGs or databases.

Cons:
More costly.. more CPU/Memory/Disk/Network has to provided, as there is no sharing.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes, you got it right ;)
25112Author Commented:
appreciate it a lot!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.