LearnPerformance

Why Is My SQL Server Slow At 3 AM?

2 min readUpdated 6 Nov 2026

Nothing is wrong in the morning and everything is wrong at 3 AM. That pattern almost always means scheduled work, not a mystery bug — the trick is proving which job caused it.

Start with the schedule, not the server

Pull the SQL Agent job history for the window and line it up against when the slowdown started. Most 3 AM problems are two or more jobs that were each fine alone: a full backup, an index rebuild, a statistics update and an ETL load all opening at the same minute.

  • Jobs that started inside the slow window, with their run duration.
  • Jobs that ran longer than their own normal duration.
  • Jobs that finished but left work behind, such as a rebuild that never committed new statistics.

Then read the waits for that window

Wait statistics tell you what the server was waiting on, which is a much shorter list than 'everything is slow'. A backup window shows up as write and I/O waits; a rebuild shows up as read waits plus lock and latch traffic; a CPU-starved load shows up as scheduler yields.

  • PAGEIOLATCH_SH — queries are waiting on data coming off disk.
  • WRITELOG — commits are waiting on the transaction log.
  • SOS_SCHEDULER_YIELD — the server wants CPU it cannot get.
  • LCK_M_S or LCK_M_X — sessions are queued behind each other.

The three usual causes

  1. 1.Maintenance and ETL share one window, so the backup and the rebuild compete for the same disk.
  2. 2.Autogrowth fires during the load, because files were sized for last month's data.
  3. 3.Blocking from a long job spills into user sessions that were supposed to be idle.

Fix the window before you fix the server. Stagger the jobs, move the backup to its own disk or its own hour, and most 3 AM pages disappear without a single index change.

What to remember

  • Line up Agent job history with the slow window first.
  • Read waits for that window, not the whole day.
  • Growth events and overlapping jobs cause most of the damage.
  • Separate the windows before changing server settings.

Related guides