I have updated the DB Sizing scripts to now collect the Availability Group name and replica state. We will now tell you if a database is a member of an AG. We also state what the role of the database on a given server, so you can see what server is primary and what it is the secondary.
I have also updated the calculations so they reflect the membership of a an AG or not.
Related Issue
83
84
Motivation and Context
This helps the SEs with their sizing process as now they be more precise.
How Has This Been Tested?
Tested in the gaia lab against standalone, FCI, and AGs
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
I have updated the DB Sizing scripts to now collect the Availability Group name and replica state. We will now tell you if a database is a member of an AG. We also state what the role of the database on a given server, so you can see what server is primary and what it is the secondary.
I have also updated the calculations so they reflect the membership of a an AG or not.
Related Issue
83
84
Motivation and Context
This helps the SEs with their sizing process as now they be more precise.
How Has This Been Tested?
Tested in the gaia lab against standalone, FCI, and AGs
Types of changes
What types of changes does your code introduce? Put an
x
in all the boxes that apply:Checklist:
Go over all the following points, and put an
x
in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!