Database Health Monitor and Azure SQL Health Monitor, Version 4.1517 This release adds ninety new reports, a drill-through navigation layer that connects them, actions that carry a fix from one instance to the rest of the estate, and a large pass over silent failures. If you knew the symptom but not the page, or fixed one server and then had to repeat the fix by hand on the other twelve, this release is aimed at you. 90 New Reports Three new …
A job slow when others run isn’t a broken package. See how Database Health Monitor’s Subsystem Load report finds the Agent worker limit causing it.
Autogrowth in percent compounds: every growth event takes longer than the last. Here’s how to spot it and fix it before it slows down SQL Server.
SQL Server technical debt turns messy T-SQL into a weighted score and a cost estimate, so you know which procedure to fix first.
A wide clustered index gets copied into every nonclustered index on the table – here is how to find the ones actually costing you.
See who changed the schema in SQL Server: the exact statement, login, host and application, captured by a DDL trigger you switch on per database.
See which SQL Server deadlock objects collide with each other, on what index, under what lock mode, and which one loses every time.
See who is connected to SQL Server right now, colored by state, so you can tell a connection leak from normal pooling before resizing anything.
Learn what signal wait time means in SQL Server wait statistics, why it signals CPU pressure, and how to read it before blaming the disk.
See which SQL Server trace flags on an instance are still doing anything on the current build, and which ones vanish at the next restart.
We are ready to help. Steve and the team at Stedman Solutions are here to help with your SQL Server needs. Get help today by contacting Stedman Solutions through the free 30 minute consultation form.
Contact Info for
Stedman Solutions, LLC.
PO Box 3175, Ferndale WA 98248,
Phone: (360)610-7833
Our Privacy Policy