Database 'SalesDB' on server 'sqlsvr01' is currently paused. Please retry the connection later. – Auto‑pause timer behavior

Direct Answer

The auto-pause timer resets after every successful query or connection, not only after the first activity following a pause. The configured delay (e.g., 60 minutes) represents a continuous inactivity window—any user query restarts that window.

Confirmed Behavior

• Serverless tier only. Provisioned compute tiers do not auto-pause.
• Each successful user query or connection resets the inactivity counter to zero.
• Background system tasks (e.g., maintenance, backups) do not reset the timer.
• When the inactivity window elapses, the database pauses. The next connection incurs a resume latency of several seconds (typically 10–60 s).

Latency Impact for Sporadic Workloads

Query Interval	Relative to Auto-Pause Delay	Observed Latency
Shorter than delay	e.g., queries every 30 min with 60-min delay	Database stays warm; no resume penalty.
Longer than delay	e.g., queries every 2 hours with 60-min delay	Each query after a pause pays the cold-start resume latency.
Near the delay boundary	e.g., queries every 55–65 min with 60-min delay	Unpredictable: some requests hit a warm DB, others trigger a pause/resume cycle.

Practical Verification (Safe, Scoped)

1. In Azure Portal, confirm the database uses Serverless compute tier and note the configured Auto-pause delay.
2. Run a query. Wait half the configured delay. Run a second query—expect normal latency (DB stayed active).
3. Wait full delay + 5–10 minutes. Run a query—expect elevated latency (resume).
4. Monitor the CPU percentage or Serverless status metric in Azure Monitor to see state transitions (Online → Paused → Online).

One Diagnostic Detail That Changes the Recommendation

What is the exact auto-pause delay configured for SalesDB on sqlsvr01? If it is set to the minimum (1 hour) and your workload issues queries every 70 minutes, you will see a resume penalty on every other request. Increasing the delay (up to 7 days) or disabling auto-pause eliminates the latency spikes at the cost of higher compute billing during idle periods.

Assumptions & Uncertainty

• Assumes Azure SQL Database serverless tier (General Purpose or Hyperscale) as of 2026-10.
• Behavior is consistent across regions; no regional variation documented.
• "Successful query" includes any authenticated connection that executes a statement; failed logins or connection attempts that error before query execution may not reset the timer (mark for review).