SQL Server down? Ring the incident line.

For retainer clients, a DBA connects and starts work within 2 hours on weekdays from 08:00 to midnight (Fridays to 18:00), and within 4 hours at weekends and on bank holidays.

Incident line

Number to follow

Say who you are, which system is affected and what you're seeing. If we can't answer at once, leave a voicemail. It reaches us straight away, and we ring you back within your response time.

Not a retainer client? Ring the same number. We help when we can, at £250 an hour with a 2-hour minimum, on a best-efforts basis with no promised response time.

Response times

  • Weekdays 08:00 to midnight (Fridays to 18:00): 2-hour response
  • Friday 18:00 to Monday 08:00, and bank holidays: 4-hour response
  • Weeknights midnight to 08:00: best efforts, with no promised response time

All times are UK time. A response means a DBA is connected to your system and working on the problem, not just acknowledging it.

What counts as an emergency

Outages, failed backups and jobs, blocking, corruption, failovers, full disks and sudden slowdowns.

Planned changes, upgrades and questions go through a normal request, so the incident line stays free for emergencies.

Raise a normal request

Have this ready

  • The server and instance name, and the database if you know it
  • The SQL Server version: run SELECT @@VERSION if you can
  • The exact error message, or a screenshot of it
  • What changed, and when the problem started
  • How we'll connect: a Teams screen share, or the access agreed when your cover started
  • Who on your side can approve changes

Before we've looked, please don't

  • Restart SQL Server again and again. A restart clears the evidence we use to find the cause, and a large database can take a long time to come back online.
  • Delete or move transaction log files, even when the disk is full.
  • Run DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS. It can delete data to make a database consistent.
  • Detach a database that won't come online. It may not attach again.

Sending logs and files

Attach logs, screenshots and query plans to your support request. For large files we send you a secure upload link: you can add files to it, but you can't see or download anything else in the folder.

Please send diagnostics, not data. Don't send database backups unless we've agreed it in writing first.