Closed BernieWhite closed 1 year ago
Still relevant to this day.
Premium ssd v2 is suited for sql server in general, but currently it has so many obscur limitations so i dont think its a really good idea to recommend this to customers, so fail on premium ssd v2 as well even if the customer has configured it, or let it slide thru?
@BernieWhite
I'm also wondering if we should target Microsoft.Compute/virtualMachines
and focus on the publisher MicrosoftSQLServer
, but that is probably not safe enough to assume Microsoft.SqlVirtualMachine/sqlVirtualMachines
.
Perhaps there is a way in PSRule to get both resources onto the pipeline in the same TargetObject?
@bengeset96 The original thought was related to performance efficiency. I think if a customer uses Premium, Premium V2 or ultra-disks that addresses the rule. A recommendation to the premium SSD or greater is enough.
@BernieWhite
I'm also wondering if we should target
Microsoft.Compute/virtualMachines
and focus on the publisherMicrosoftSQLServer
, but that is probably not safe enough to assumeMicrosoft.SqlVirtualMachine/sqlVirtualMachines
.Perhaps there is a way in PSRule to get both resources onto the pipeline in the same TargetObject?
Targeting by publisher is probably the best. It's not really possible to see both related objects.
@BernieWhite
Sounds great. This means that we will be able to test osDisk and dataDisks defined within storageProfile
.
We wont be able to target disks from Microsoft.Compute/disks
or Microsoft.Storage/storageAccounts
I assume since there is nothing here that gives us the information we're seeking, but that option is most likely not so widely used for this scenario.
Check that IaaS SQL VMs only use premium disk.