You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix invalid DMV columns in three report functions (1.6.4.0)
Found via live runs against a local SQL 2022 plus a static validation of every DMV query through
sys.dm_exec_describe_first_result_set.
- Get-sqmMissingIndexes: join used mid.index_group_handle, which does not exist in
sys.dm_db_missing_index_details (only index_handle). Fixed to mid.index_handle = mig.index_handle.
- Get-sqmOperationStatus: AutoSeed query used non-existent columns total_size_bytes / start_time /
estimated_completion_time_ms from sys.dm_hadr_physical_seeding_stats. Switched to the real columns
database_size_bytes / start_time_utc / estimate_time_complete_utc (remaining time via DATEDIFF ms),
aliased to the names the PowerShell side expects.
- Get-sqmAlwaysOnFailoverHistory: optional SQL supplement read ars.role_start_time, which does not
exist in sys.dm_hadr_availability_replica_states. Replaced with the valid column
current_configuration_commit_start_time_utc (UTC approximation; Event Log 1480 stays authoritative),
plus UTC comparison and NULL guard.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments