Use the Involved In Replication health check in Mini DBA to review Azure SQL Database configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for resource configuration or pressure that can limit performance as concurrency or workload volume increases.
Capacity problems are easier to fix before the instance is saturated. This check helps identify where configuration or workload growth is reducing headroom.
Compare current configuration with workload demand and host capacity. Tune the setting, reduce wasteful concurrency, address top queries, or resize the instance when the workload has outgrown the available resources.
Keep a short baseline of resource use and concurrency before changing limits or resizing. This makes it easier to distinguish real growth from an abnormal spike.
Prioritize it according to workload criticality and trend. A one-off warning may be scheduled maintenance, but repeated failures usually deserve an owner and target date.
Prevent repeat failures by reviewing capacity trends alongside alert history. If the same check returns after each fix, treat it as a sizing or design issue rather than a one-off maintenance task.
Add this page to the operational runbook for Azure SQL 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.