Free audit

View Audit Scope
SQL ServerRemote DBA, support, and scoped projects

SQL Server database services for production teams.

JusDB provides SQL Server services for scoped projects, remote DBA coverage, production support, performance tuning, migrations, and high availability. We work on Azure SQL Managed Instance, Amazon RDS, Azure and AWS virtual machines, and your own Windows or Linux servers. 24x7 on-call is available under your service agreement.

Or request a free audit of one database instance. Already in an incident? See SQL Server support.

  • NDA before access
  • Read-only by default
  • Changes measured against your baseline

SQL Server version status

Pick the version you run

SQL Server 2025

Newest release

Generally available since 18 November 2025, with mainstream support to January 2031 and extended support to January 2036.

SQL Server 2014 SP3, 2016 SP3, and later versions can upgrade in place to 2025 without stopping at 2019 or 2022.

Plan a SQL Server upgrade

Version status from Microsoft's SQL Server lifecycle pages and the Amazon RDS for SQL Server version page, checked 28 October 2026.

Platforms
Azure SQL, Amazon RDS, cloud virtual machines, and your own Windows or Linux servers
High availability
Always On availability groups, failover cluster instances, and log shipping
Incidents
Initial-response targets are set in your service agreement. See the targets

Symptoms

Eight SQL Server problems we are asked to fix

Each one has a cause we can measure. The scoping call starts from the symptom you see and the version and platform you run.

  1. A query that took seconds yesterday takes minutes today after a statistics update or recompile changed its plan, and nobody has compared the plans in Query Store.

  2. The transaction log grows until the disk fills and nobody has checked log_reuse_wait_desc, which names the cause: missing log backups, a long-running transaction, or a lagging secondary replica.

  3. Blocking chains stall the application at peak load because readers and writers block each other under the default isolation level, and nobody has traced the head of the chain.

  4. Sessions pile up on PAGELATCH waits in tempdb because temporary-table churn contends on the allocation pages (PFS, GAM, and SGAM), and tempdb has too few equal-size data files.

  5. The upgrade off SQL Server 2016 keeps slipping after extended support ended on 14 July 2026, and SQL Server 2017 follows in October 2027.

  6. Small queries run in parallel and tie up worker threads because cost threshold for parallelism is still 5, the default, so CXPACKET and CXCONSUMER waits dominate.

  7. A readable secondary serves stale data during index maintenance because redo falls behind the log from large index rebuilds, and that backlog would also lengthen a failover.

  8. Backup jobs report success, but nobody has restored one and DBCC CHECKDB runs less often than backups expire, so clean copies can age out before corruption is found.

If one of these is costing your team time, a scoping call is the place to start.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Failover

How an untested failover loses SQL Server commits

The primary does not wait for an asynchronous-commit secondary, so that replica can lack commits your application was told are saved. A synchronous-commit secondary that misses the session timeout (10 seconds by default) is marked NOT SYNCHRONIZING, and the primary commits without it.

One primary, two secondaries, three outcomes

Choose a state to see where the commits go.

Applications and the listener

Applications connect through the listener with MultiSubnetFailover=True, and read-intent connections go to a readable secondary.

Commits on two replicas
  • Primary

    Takes every write

    Healthy

  • Secondary 1

    Synchronous commit: has each commit before it is confirmed

    SYNCHRONIZED

  • Secondary 2

    Asynchronous commit, in another region for disaster recovery

    Slightly behind

Automatic failover can go to Secondary 1 only while it is SYNCHRONIZED and the cluster has quorum.

We pair the primary with a nearby synchronous-commit secondary for automatic failover, and asynchronous replicas elsewhere for disaster recovery. We alert when a synchronous secondary leaves the SYNCHRONIZED state, or when a disaster recovery replica's last_commit_time trails the primary by more than your recovery point objective (RPO).

Where a commit must never run unprotected, we set REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT (SQL Server 2017 and later), which makes commits fail when too few secondaries are synchronized. We script logins and SQL Server Agent jobs to every replica, or keep them in a contained availability group on SQL Server 2022 and later. We rehearse planned and forced failover on a copy first.

What we cover

Full-spectrum SQL Server engineering

Wait statistics, Query Store, and execution plans drive every change, from one slow report to a version upgrade.

  • Performance tuning

    We read execution plans and wait statistics before changing anything, then measure each change against your baseline.

    • Query Store plan forcing where a plan regressed
    • Wait statistics, tempdb contention, and memory grants
    • MAXDOP and cost threshold for parallelism set for your hardware
    SQL Server performance tuning
  • High availability and DR

    Failover designed around the data loss and downtime your business can accept (RPO and RTO), then drilled.

    • Always On availability groups with read-only routing
    • Failover cluster instances and log shipping
    • Planned and forced failover rehearsed on a copy
    SQL Server high availability
  • Replication and AG setup

    Read traffic sent only to secondaries that can serve it.

    • Readable secondaries behind read-only routing
    • Distributed availability groups across regions
    • Transactional replication for reporting copies
  • SQL Server expertise

    Microsoft and community tools, set up so your team can keep running them.

    • Ola Hallengren's scripts for backups, integrity checks, and index maintenance
    • dbatools for scripted migrations and instance checks
    • Extended Events sessions for diagnosing incidents
    SQL Server remote DBA
  • Cloud migration

    Version upgrades and platform moves with a tested way back (a rollback plan).

    • Upgrades off 2016 and 2017 to 2022 or 2025
    • Moves to Azure SQL or Amazon RDS
    • Log shipping, distributed availability groups, or AWS DMS cutovers
    SQL Server migration
  • Security and compliance

    Access, encryption, and audit settings reviewed against the controls your auditors ask about.

    • Least-privilege logins and roles, with few sysadmin members
    • Transparent data encryption (TDE), Always Encrypted, and TLS
    • SQL Server Audit, with control mapping your auditors can read

Incident support

A critical (P1) page, answered within your agreement's target

JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.

Initial-response targets

  • 2 to 4 hours

    Business hours

    During covered business hours

  • 15 minutes

    24x7 on-call

    P1 incidents

P1 · Critical15 minutes

Production database down, primary unreachable, data corruption risk, or active failover event.

P2 · High30 minutes

Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.

P3 · Medium60 minutes

Non-critical slow query regression, staging issue, backup warning, or replication check alert.

P4 · Low90 minutes

Configuration question, index advisory, planned schema review, or general operational request.

Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.

Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.

What happens on a P1 page

  1. Page

    You page the on-call engineer

    Through the escalation path your service agreement names.

  2. Triage

    Root cause from wait statistics and Query Store

    Blocking chains, plan regressions, and runaway sessions traced to the statement behind them.

  3. Mitigate

    Stabilize first, from the runbook

    Kill the head blocker, force the last good plan, or fail over, then fix the cause once production is steady.

  4. After

    A review after every P1

    What happened, why, and the change that stops it happening again.

Before and between incidents

  • Your setup, written down firstDuring onboarding we record your versions, editions, availability groups, listeners, and backup jobs, so an incident starts with context.
  • One escalation path, in writingYour service agreement names how to reach the on-call engineer, in which hours, and who approves a forced failover.
  • Reviews between incidentsWe review wait statistics, plan regressions, availability group health, capacity, and DBCC CHECKDB results, and report open risks.
  • Version dates trackedWe track Microsoft lifecycle dates and cumulative updates for your versions, and plan upgrades before extended support ends.

Process

How a SQL Server engagement runs, step by step

Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.

  1. Scoping call

    Your databases, versions, editions, platforms, and what you need covered.

  2. Read-only review under NDA

    Our engineers use named accounts with only the permissions the review needs, such as VIEW SERVER STATE, then read your configuration, wait statistics, Query Store, and availability group state.

  3. A written report before any change

    Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).

  4. Changes, then handover

    We rehearse risky changes on a restored copy, patch secondaries first, and measure each change against the baseline, then hand over updated operating instructions (runbooks).

Ways to work

Choose the SQL Server service your team needs

Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.

Where your SQL Server runs, and the tools around it

Your team and ours

What a managed SQL Server service still leaves to your team

Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.

Who handles each part of running SQL Server on a managed service and on your own servers
QuestionManaged cloud serviceYour own servers or Kubernetes
Servers, storage, and patchingThe provider runs them and supplies engine updates.Your team, or JusDB under your agreement.
Backups and restoresAutomated backups and point-in-time restore are built in. Testing a restore is still your team's job.Your team schedules full, differential, and log backups for point-in-time restore.
FailoverThe provider runs it. Your application still has to reconnect cleanly.You choose it and run it: availability groups, failover cluster instances, or log shipping.
Slow queries, blocking, and index maintenanceYours. The provider runs the platform, not your queries.Yours.
Versions and end of supportThe provider's calendar. Amazon RDS schedules an automatic upgrade for versions it stops supporting.Your calendar. After extended support ends, only Extended Security Updates bring security fixes.
Moving off laterA native backup where the service allows one, such as RDS backups to Amazon S3.Full and log backups, log shipping, or a distributed availability group move the databases.

Your team keeps control

  • Set business priorities, application requirements, and release plans
  • Approve production changes, except routine actions you have pre-approved
  • Own your cloud accounts, access policies, and vendor relationships
  • Decide when maintenance can happen and how quickly service must recover
  • Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)

JusDB handles the agreed database work

  • Monitor database health, investigate alerts, and involve the right people
  • Review query performance, replication, capacity, and backup health
  • Carry out approved changes and update the operating instructions they affect
  • Report completed work, open risks, and recommended next steps

Weighing Azure SQL or Amazon RDS against running SQL Server yourself? We compare them against your workload on a scoping call.

Book a 30-min scoping call (opens Google Calendar in a new tab)

Further reading

SQL Server guides for maintenance, Azure, and Amazon RDS

Guides from our blog on maintenance, Azure SQL options, and Amazon RDS, plus comparisons with PostgreSQL and MySQL.

FAQ

Common SQL Server questions

What buyers ask about SQL Server coverage, versions, cutovers, and platforms.

Still have a question?

Ask it on a scoping call. No production access needed.

Book a 30-min scoping call (opens Google Calendar in a new tab)

How does this hub relate to your Support and Remote DBA services?

This page is JusDB's overview of all SQL Server work. SQL Server support handles incidents up to a critical (P1) outage, with 24x7 on-call available under your service agreement. Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees. SQL Server remote DBA covers monitoring, maintenance, backups, and capacity planning.

What versions of SQL Server do you support?

JusDB supports SQL Server 2014 through 2025 on Windows, and 2017 through 2025 on Linux. On 2014 and 2016, both past extended support, we work on production instances while you plan the upgrade.

How do you plan a SQL Server migration cutover?

JusDB plans each SQL Server migration as a rehearsed cutover to a target kept in sync beforehand, with a rollback plan. A Query Store baseline taken before the compatibility level is raised lets us force a regressed query back to its earlier plan. JusDB does not guarantee a cutover duration.

How quickly can you start?

JusDB starts work once the scope is agreed and access is in place, on a date confirmed in your proposal. If you are not yet a client and SQL Server is failing now, send us the incident details. We review enquiries within 2–4 business hours, Mon–Fri 09:00–18:00 IST.

Do you handle both on-prem and cloud SQL Server?

Yes, JusDB handles SQL Server on your own physical servers and VMware virtual machines. In the cloud we cover Azure SQL Managed Instance, Azure SQL Database, Amazon RDS, and Azure or Amazon EC2 virtual machines, plus hybrid setups.

Next step

Talk to a SQL Server engineer about your databases

Tell us what is slow, fragile, or due to change. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.

NDA before access, read-only by default, and written scope first