November 22, 2017 at 11:11 am
Is it common to put all/ majority of SQL Servers in a resource group or have separate resource groups for each SQL Server. (SQL Server on VM)
I'm trying to determine if Web/App servers should be in their own RG and the DB servers should be in a RG?
OR
Web/App and DB have their own RG?
I'm expecting to eventually have over 100 db servers in the "prod" subscription.
thoughts anyone?
November 22, 2017 at 11:24 am
Hey ggoble,
It's my understanding that you want to have resource groups with your systems that are directly dependent on each other. So you have it right when you say the WebApp and DB should be in the same resource group. This probably explains the benefits better, https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview, but one of the benefits we've taken advantage of is the fact that you can completely clean up an application by simply deleting the resource group.
That said, you can group your resources however it makes the most sense for you.
I hope that helps,
Steve
November 24, 2017 at 1:22 pm
I agree with the previous answer. Group by functionality and purpose, not by technology. You might have a Testing resource group, for example, on which you run validations prior to moving it into a Production resource group or a MyApplication resource group. Whatever, but the grouping is by broad functionality, not by tool.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply