Which component(s) does this affect?
Problem Statement
The FinOps pages provide a lot of super useful information. I often also check growth rates and Virtual Log File (VLF) counts.
Proposed Solution
On the Databases Sizes page* of FinOps, include additional columns for:
- Data/log file growth value and units (percent/MB).
- Log file VLF counts. (Data file rows may need to show "N/A").
*This page/screen seems to me like it would be the best spot. But I'm open to your preference to put it somewhere better.
Scripts attached for values I'm suggesting. Although these probably need to be adapted to work for all Azure SQL Databases in a "logical server".
PM-Enhancement-VLFs.sql
PM-Enhancement-GrowthSettings.sql
Use Case
A1. Navigate to the Database Sizes screen.
A2. Order by VLF count (Descending) and resolve any databases with high counts.
B1. Navigate to the Database Sizes screen.
B2. Identify any files with percent growth and correct.
C1. Navigate to the Database Sizes screen.
C2. Identify any files where growth increments are too large or too small - and correct.
Alternatives Considered
Run script manually outside of Performance Monitor.
Additional Context
- All supported versions - 2016+
Which component(s) does this affect?
Problem Statement
The FinOps pages provide a lot of super useful information. I often also check growth rates and Virtual Log File (VLF) counts.
Proposed Solution
On the Databases Sizes page* of FinOps, include additional columns for:
*This page/screen seems to me like it would be the best spot. But I'm open to your preference to put it somewhere better.
Scripts attached for values I'm suggesting. Although these probably need to be adapted to work for all Azure SQL Databases in a "logical server".
PM-Enhancement-VLFs.sql
PM-Enhancement-GrowthSettings.sql
Use Case
A1. Navigate to the Database Sizes screen.
A2. Order by VLF count (Descending) and resolve any databases with high counts.
B1. Navigate to the Database Sizes screen.
B2. Identify any files with percent growth and correct.
C1. Navigate to the Database Sizes screen.
C2. Identify any files where growth increments are too large or too small - and correct.
Alternatives Considered
Run script manually outside of Performance Monitor.
Additional Context