Use the Old Compatability Level health check in Mini DBA to review SQL Server Database configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for version or compatibility drift that can affect supportability, security patching, and feature availability.
The check turns an operational best practice into a repeatable Mini DBA review item so teams do not rely on memory or occasional manual audits.
Plan an upgrade or compatibility review, test application behavior in a lower environment, and schedule the change through the normal release process.
Keep a short note explaining why the check failed, what was changed, who owns the follow-up, and whether an exception was approved.
Prioritize it by blast radius. Fix it quickly when it affects a production workload, a shared server, or a customer-facing service; otherwise place it in the normal improvement backlog with an owner.
Prevent repeat failures by assigning an owner, documenting the expected configuration, and reviewing the check after upgrades, migrations, or major application releases.
Add this page to the operational runbook for SQL Server Database environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.