SQL Server support

SQL Server Support for Always On, Failover Clusters and Version Upgrades

Last reviewed by Tyler Eastridge

AceMQ supports SQL Server 2016 to 2025, 24/7, on Windows and Linux, in standalone, failover cluster and Always On estates. Most calls start with one of three problems: blocking chains that time out an application, a full transaction log (error 9002), or an availability group that stops synchronising. Upgrades are planned and tested before production.

AceMQ provides 24/7 SQL Server support for versions 2016 to 2025, with a senior engineer on a live bridge for a P1 (response targets from 15 minutes, by plan). SQL Server 2016 extended support ended on 14 July 2026, so we also plan the upgrade or the Extended Security Updates route and test it before production. The work is delivered with partner SQL Server specialists, under one AceMQ SLA.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ SQL Server consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

SQL Server problems we fix every week, and what a DBA checks first

Seven SQL Server symptoms, each with the DMV, log or catalog view a DBA opens first: wait stats, deadlock reports, replica state and backup history.

Common SQL Server production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Queries wait with RESOURCE_SEMAPHORE, memory grants queue upsys.dm_exec_query_memory_grants for requested against granted memory, then the plans asking for large sorts or hashesFix the estimate (statistics, a missing index), then Resource Governor limits if one workload dominates
Deadlock errors (1205) climb after a releaseThe xml_deadlock_report event in the system_health session: the two statements and the lock orderConsistent access order, a covering index, or a shorter transaction
Everything pauses for seconds during file growthAutogrowth settings in sys.database_files, and whether instant file initialization is enabled for the service account (data files only; log files are always zeroed)Pre-size files, grow in fixed MB, grant the volume maintenance right
Availability group secondary is minutes behindsys.dm_hadr_database_replica_states: log_send_queue_size against redo_queue_size separates a network or primary problem from a slow redo on the secondaryNetwork or redo thread fix; a read workload on the secondary blocking redo is common
Failover cluster instance moves repeatedlyCluster log and the SQL Server health check timeout against the failure condition level, then storage latency at the moment of failoverFix the underlying stall before loosening the failure condition
Backup job succeeds but a restore test failsmsdb.dbo.backupset chain for a gap in the log backups, then RESTORE VERIFYONLY and a real restore to a scratch serverRepair the chain, add a scheduled restore test, run DBCC CHECKDB on the restored copy
A cumulative update fails halfwaySetup logs and the SQL Server error log from the failed start, then whether a service, mirror or availability group blocked script upgrade modeRoll back or complete the script upgrade, then retry in a window with rollback ready

A production incident ends with an RCA that cites the wait type, log entry or configuration behind it and the change made.

Availability group failing over or the log file full? Request a quote and a DBA replies within an hour.

Contact Us

Deployment coverage

Which SQL Server deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the platform vendor coversExcluded
SQL Server on Windows Server or Linux, on-premises24/7 incident response, root cause analysis on P1s, performance, backup and restore checks, patch and upgrade planningMicrosoft supplies updates and, for older versions, paid Extended Security UpdatesMicrosoft patches, which AceMQ does not produce
Failover cluster instancesCluster and instance behaviour, failover testing, storage latency reviewWindows Server Failover Clustering product defectsStorage array and SAN faults outside the scope
Always On availability groups and log shippingSynchronisation health, listener and MultiSubnetFailover connection problems, failover runbooksProduct defectsNetwork faults outside the scope
VMware vSphere, Azure VMs, AWS EC2The SQL Server layer, plus sizing of memory, CPU and storage as seen from SQL ServerThe platform provider runs the platformProvider faults
Azure SQL Managed Instance and Amazon RDS for SQL ServerWorkload, query and design helpThe provider runs the service and its upgradesAnything needing provider-side access
Air-gapped sitesSupport through your jump host and exported diagnosticsNot applicableTools that need outbound access

Support options

Who provides enterprise support for SQL Server?

Microsoft provides enterprise support for SQL Server through its own support plans, and it alone ships cumulative updates, security updates and Extended Security Updates. Independent support from AceMQ supplies senior engineers for incidents, tuning and upgrades, 24/7, with response targets from 15 minutes, by plan.

Microsoft
AceMQ independent support
What it coversThe product: updates, security fixes, product defects
What it coversThe estate: your instances, your workload, your application's queries
Root cause analysisPer Microsoft process
Root cause analysisWritten RCA on every P1
PriceSet by the Microsoft agreement
PriceQuoted per engagement; quote reply within 1 hour
Application and query tuningOutside product support
Application and query tuningIn scope
Product defectsMicrosoft fixes
Product defectsWe diagnose and take the escalation with you

What's Included

Everything in your SQL Server support contract

Instances, failover cluster instances, Always On availability groups and the maintenance, patching and recovery work around them.

  • 01

    Emergency Incident Response

    Instance down, failover stuck, the log full, blocking or a restore that will not finish. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge, 24/7, with access to diagnose, not a ticket acknowledgement.

  • 02

    Always On and Failover Cluster Support

    Replica modes, quorum, lag against your recovery point objective, listener and connection string behaviour, and login and job synchronisation. We rehearse failover on a non-production copy rather than discovering the gaps during an outage.

  • 03

    Performance and Query Store Review

    Wait statistics first, then the queries behind them: regressed plans, parameter sniffing, statistics, parallelism settings, tempdb layout and memory. Fixes are proposed with evidence, not guesses.

  • 04

    Backup, Restore and CHECKDB Verification

    The backup chain, the retention against your recovery objectives, restore tests on a scratch server and the date of the last clean DBCC CHECKDB for each database. A backup nobody has restored is a hope, not a plan.

  • 05

    Cumulative Update and Security Advisory

    Which cumulative update and security fixes apply to the exact versions you run, a tested rollout order, and the evidence an auditor asks for. For SQL Server 2016, the steps to subscribe to Extended Security Updates.

  • 06

    Upgrade Planning

    SQL Server 2016 and 2017 to a supported release: inventory, compatibility level and Query Store testing, a rollback plan and a cutover window. Microsoft's own migration guidance is the reference, and we test it against your workload.

Why AceMQ

What our SQL Server DBAs add

  • One SLA, One Escalation Path

    AceMQ holds the contract and response targets from 15 minutes, by plan, and brings in partner SQL Server specialists as the problem needs them. You are never handed between companies in the middle of an incident.

  • No Help-Desk Layer

    You reach a senior engineer directly by phone, email or Slack. No agent collecting details to relay, and no approval step between you and someone who can read a wait-statistics snapshot and act on it.

  • The Application Is in Scope

    Many SQL Server incidents start in what the application does: transactions held open across a call, chatty connections, parameterised queries with skewed data. We look at the database and the workload that drives it.

  • Honest About What We Cannot Patch

    SQL Server is Microsoft's. We do not offer patched builds, and we say so. Extended Security Updates come from Microsoft; we plan the route, test it and support the instance around it.

SQL Server platforms covered

Windows and Linux instances on VMware, Azure VMs, AWS EC2 and physical servers, plus design help for the managed Azure and RDS offerings.

  • SQL Server on Windows Server and on Linux
  • Standalone instances and failover cluster instances
  • Always On availability groups and log shipping
  • VMware vSphere virtual machines
  • Azure virtual machines
  • AWS EC2 instances
  • On-premises servers and bare metal
  • Air-gapped / no outbound access
  • Azure SQL Managed Instance and Amazon RDS for SQL Server (workload and design help; the provider runs the platform)

Version coverage

Versions we support

Versions we support
SQL Server versionMicrosoft free security updates throughAceMQ coverage
20256 January 203624/7 support
202211 January 203324/7 support
20198 January 2030 (Redmond date; Microsoft lists 1/9/2030 06:59 UTC)24/7 support
201712 October 202724/7 support and upgrade planning
2016Paid Extended Security Updates only, from 15 July 202624/7 support, ESU enrolment help and upgrade planning

Source: Microsoft Learn lifecycle pages (SQL Server 2019 page read 17 Nov 2026; other rows from the live page, read 31 Oct 2026).

In practice

How do you plan a SQL Server upgrade without downtime?

You plan it so the only outage is a failover, not a restore. For a standalone instance that means a side-by-side migration with log shipping or backup and log restore, cut over in a short window. For an availability group it means upgrading a secondary first, then failing over. Microsoft documents that once a secondary runs a newer version, the group can fail over to it but cannot fail back to the older version, so rollback must be planned before the failover, not after.

An AceMQ upgrade plan contains:

An inventory: version, edition, compatibility level, features in use, linked servers, jobs, logins and drivers.

A compatibility test at the target version with Query Store open, so a regressed plan is visible and can be forced back as a stopgap.

A rehearsal on a copy of production data and the real workload.

A cutover runbook with a rollback per step and a named decision point.

A first-week review of waits, plans and errors against the pre-upgrade baseline.

Downtime is the failover window, usually seconds to minutes. It is not zero, and a plan that promises zero has not read the connection strings.

First checks

Eight SQL Server symptoms, and what a DBA checks first

A diagnostic map for the symptoms that bring SQL Server teams to a support desk: the first thing we look at and the usual type of fix. It is a map for your own team as well as ours, not a log of past incidents.

  • Dozens of sessions are waiting and the application times out

    A blocking chain: find the head blocker with sys.dm_exec_requests (blocking_session_id) and sys.dm_tran_locks, then see what its open transaction is doing. Usually it is a transaction held open across a slow call, an unindexed update or an escalated lock, not the SQL Server itself. Usual fix: shorter transactions, an index, or row-versioning isolation, after the head blocker is dealt with.

  • Error 9002: the transaction log is full

    Query log_reuse_wait_desc in sys.databases. LOG_BACKUP means log backups are not running in the full recovery model. ACTIVE_TRANSACTION means a long-running or deferred transaction. AVAILABILITY_REPLICA means a secondary has not applied the log yet. Shrinking the file before the wait reason is fixed only repeats the problem. Usual fix: fix the wait reason, take the log backup, then size the log properly.

  • A query that was fast is now slow after an upgrade, a patch or a compatibility level change

    Query Store, where the previous plan is still on record: compare plans for the query and look at runtime statistics around the change. A regression can be forced back to the last good plan as a stopgap while the cause (statistics, a changed estimate, parameter sniffing) is found. Usual fix: plan forcing as a stopgap, then the statistics, index or query fix.

  • An availability group database shows NOT SYNCHRONIZING or the send and redo queues keep growing

    sys.dm_hadr_database_replica_states for the synchronization state, queue sizes and last_commit_time of every secondary. A suspended database on a secondary delays log truncation on the primary, so the log can fill while you look at the replica. Network, redo thread blocking and disk latency on the secondary are the usual causes. Usual fix: resume or reseed the secondary, and fix the network, disk or blocking cause.

  • Failover happened, but the application cannot connect or jobs and logins are missing

    Whether the application connects through the availability group listener, and whether the connection string sets MultiSubnetFailover for a multi-subnet listener. Microsoft notes that, except for contained databases, logins and jobs on the former primary must be recreated on the new one, so we compare them across every replica. Usual fix: listener and connection string changes, plus login and job synchronisation.

  • PAGELATCH waits on tempdb at peak load

    Allocation contention on a few system pages. We compare the number and size of tempdb data files, which should be equal, against the core count, and look at what is creating and dropping temporary objects at that rate. Modern versions create several files at setup, but older installs are often left at one. Usual fix: equally sized tempdb files, and the workload that hammers them.

  • DBCC CHECKDB reports corruption, or a restore fails partway through the chain

    Which pages are damaged, when the last clean CHECKDB and backup were, and whether the log chain is unbroken. We do not reach for REPAIR_ALLOW_DATA_LOSS first. Restoring from the last good chain to a scratch server shows what a recovery really takes. Usual fix: restore from a clean chain, then find the storage or memory cause.

  • CPU is pegged and CXPACKET or CXCONSUMER waits dominate

    Cost threshold for parallelism (the default is 5, which Microsoft calls a starting point) and MAXDOP against the core count, then the top CPU queries in Query Store. Too many small queries going parallel is a common cause, as are missing indexes and stale statistics. Usual fix: parallelism settings and the worst queries, before any cores are added.

Something not on the list? Tell us what is breaking and a senior engineer will take it. SQL Server DBA services

SQL Server 2016

SQL Server 2016 is out of extended support: what to do about it

Since 14 July 2026 SQL Server 2016 has had no free security updates. You can upgrade, or buy time with Extended Security Updates. The four points below set out both.

  • Upgrade, the durable answer

    Move to SQL Server 2022 or 2025, or to Azure SQL Managed Instance. Test the application at the new compatibility level with Query Store open so a regressed plan is visible, and keep a rollback path until the new version has run a full business cycle.

  • Extended Security Updates through Azure Arc

    Microsoft's article says ESUs for SQL Server 2016 are available when an instance is connected to Azure Arc, with Software Assurance on an Enterprise Agreement, Enterprise Agreement Subscription, Server and Cloud Enrollment or Enrollment for Education Solutions, or with pay-as-you-go billing without Software Assurance. Azure bills hourly, and the subscription ends when you upgrade.

  • ESUs on SQL Server on Azure VMs

    Instances on Azure virtual machines subscribe through the SQL IaaS Agent extension. Microsoft states that SQL Server 2016, unlike 2014, does not get free ESUs by moving to an Azure VM, so this is a subscription too.

  • What an ESU is not

    ESUs cover vulnerabilities Microsoft rates Critical, with no regular schedule, and no new features or fixes you asked for. They do not include support for the underlying SQL Server version. Microsoft advises installing and validating the latest cumulative update when you subscribe, not when the first ESU ships.

Dates, options and a checklist for this week are in the full guide. SQL Server 2016 end of life

Escalation Path

Your first hour of a SQL Server outage

The DBA who answers a log-full alarm or a lagging secondary has read sys.dm_hadr_database_replica_states before and starts there.

  1. From 15 min (by plan)first responseEmergencyInstance down or failing over repeatedly, availability group unable to resume, transaction log full on a production database
  2. 1 hourfirst responseCriticalMemory grants queuing on RESOURCE_SEMAPHORE, secondary replica minutes behind, failed backup chain
  3. 4 hoursfirst responseHighDeadlocks rising after a release, stalls during file growth, cumulative update failing midway
  4. Next Dayfirst responseStandardQuestions on index design, upgrade path, autogrowth settings and maintenance plans

Targets scale with your plan. A failover cluster instance flapping at month end and a question about instant file initialization get different clocks.

Want named SQL Server DBAs behind your instances? Get a quote or send us a message.

Contact Us

Pricing

What does AceMQ SQL Server support cost?

SQL Server support usually costs $24,000 to $72,000 a year, quoted per scope. It follows how many instances and availability groups are in production, the criticality of each database, and the response level.

Prices are in USD. Response targets start at 15 minutes depending on plan, 24/7, and quote requests are answered within 1 hour. A multi-technology discount applies if PostgreSQL or other databases join the contract.

Typical engagements

SQL Server problems we have solved

Cases where SQL Server was part of the estate: change data capture and messaging around SQL Server sources, plus typical-engagement scenarios that describe how an AceMQ SQL Server engagement runs. Scenario cards are marked as service use cases, not past customers.

1 / 6 case studies

  • Support

    Debezium MySQL Binlog Retention and Schema History Support

    Online Travel Platform

    Ongoing support for a MySQL change data capture pipeline that needed a full re-snapshot after a planned outage outlasted binlog retention and a trimmed schema history topic.

    DebeziumMySQLSQL ServerOracle DatabaseKafkaAmazon RDS
  • Assessment

    SQL Server Always On Availability Group Failover Review

    Regional Logistics Operator

    A typical engagement: reviewing an Always On availability group that spans two sites, so the first real failover is not the first test of its replica modes, quorum and lag tracking.

    SQL ServerWindows Server Failover ClusteringAlways On Availability Groups
  • Managed Services

    Managed SQL Server in the Customer's Own Cloud Account

    SaaS Platform Team

    A typical engagement: AceMQ takes over operations of a SaaS platform's SQL Server estate in the customer's own AWS account, with the data and the licences staying with the customer.

    SQL ServerAmazon EC2Always On Availability Groups
  • Assessment

    SQL Server Health Check Before an Upgrade or Migration Decision

    Professional Services Firm

    A typical engagement: a read-only health check of a SQL Server 2016 and 2017 estate, so the team can choose between upgrading, Extended Security Updates and a move on evidence about backups, configuration and version position.

    SQL ServerQuery StoreSQL Server Agent
All use cases

Support options

Four tiers of SQL Server support.

AceMQ offers SQL Server support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident response for servers your team runs, proactive reviews of backups, restores, availability groups and patch level, managed SQL Server on your own infrastructure, and fully managed SQL Server on AceMQ infrastructure. Work is delivered with partner SQL Server specialists under one AceMQ SLA. SQL Server 2016 to 2025 is covered, and Microsoft's Extended Security Updates remain Microsoft's.

  • Tier 1

    SQL Server 24/7 Support & Incident Management

    Your DBAs run it, we back them up

    Best for: Teams with in-house DBAs who want a senior engineer for blocking, failover and log-chain emergencies.

  • Tier 2

    SQL Server 24/7 Support with Proactive Monitoring

    We check waits, backups and patch levels

    Best for: Teams whose restore tests, memory grants and cumulative updates only get attention when something breaks.

  • Tier 3

    Managed SQL Server on Your Infrastructure

    We administer instances you host

    Best for: Organizations needing backups, patching and monitoring handled on servers inside their own network.

  • Tier 4

    Fully Managed SQL Server on AceMQ Infrastructure

    We run your SQL Server instances for you

    Best for: Teams that want the databases available without hiring DBAs for patching and recovery.

FAQ

SQL Server support questions

Answers on SQL Server support from AceMQ: what the 2016 end of extended support means, who provides Extended Security Updates, what is included and who delivers it.

Still have questions about SQL Server? Email an Expert

Who provides enterprise support for SQL Server?

Microsoft supplies updates and product support under its own plans. AceMQ supplies senior engineers, 24/7, for incidents, tuning, backups and upgrades, with response targets from 15 minutes, by plan. Most estates use both.

How do you plan a SQL Server upgrade without downtime?

Rehearse on a copy, test at the new compatibility level with Query Store, upgrade an availability group secondary first and fail over. Downtime shrinks to the failover window. See section 6.

What does 24/7 SQL Server support cover?

Round-the-clock DBA response, starting within 15 minutes on the top plans, covering incidents, performance, patching and recovery. A Sev 1 sample: an availability group secondary stops hardening log. We read log_send_queue_size and redo state, restore sync, and write an RCA. P2 is 1 hour, P3 4 hours, P4 next business day.

Can you support SQL Server 2016 now that free security updates stopped?

Yes. We support it 24/7, help enrol in Extended Security Updates and plan the move to 2022 or 2025.

Does support include routine DBA work such as backups?

Support covers reviewing and testing backups and restores and fixing failures. Doing the schedule every day is managed services, at /sql-server/managed-services/.

Why does the transaction log fill up (error 9002)?

Query log_reuse_wait_desc in sys.databases: LOG_BACKUP, ACTIVE_TRANSACTION and AVAILABILITY_REPLICA each have a different fix. Shrinking first only repeats the problem.

Can you tune SQL Server performance?

Yes: Query Store, wait statistics and the top queries by CPU and reads. A fixed-scope review is described at /sql-server/health-check/.

Which platforms do you support?

Windows Server, Linux, VMware, Azure VMs, AWS EC2, and on-premises hardware. For Azure SQL Managed Instance and RDS we help with workload and design.

Can we engage you on SQL Server for one project?

Yes. One-off work such as a health check, a wait-statistics investigation or an upgrade between versions needs no yearly term. An annual agreement adds 24/7 response and the same named DBAs on every call, which suits databases behind revenue systems.

What determines SQL Server support pricing?

Contracts generally run $24,000 to $72,000 a year (USD). We scope by instance count, whether Always On availability groups or failover cluster instances are used, how critical the databases are, whether routine DBA work is included, and response level. A quote follows within 1 hour of your request.

Let's talk

Planning an upgrade or short of a DBA tonight?

Tell us the version and the topology. We quote per engagement and reply within 1 hour.

A senior SQL Server engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a SQL Server Architect