Use the Wildcard used to begin search 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 design or query-pattern choices that can make execution plans harder to optimize and troubleshoot.
Plan quality problems often appear as intermittent performance incidents. This check helps you find the design issue while there is time to tune it deliberately.
Inspect the affected code path and recent execution plans. Prefer query rewrites, indexing, statistics fixes, and application changes over broad server settings unless the workload has been tested.
Keep before-and-after evidence such as execution plans, runtime, reads, writes, and index usage so the change can be judged by workload impact rather than preference.
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 adding the finding to the normal performance review cycle. Query and index checks are most useful when developers and DBAs share the same evidence and agree on the expected workload pattern.
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.