Free audit

View Audit Scope
SQL ServerArchitecture, tuning & licensing audits

SQL Server Consulting Services & Architecture Review

JusDB provides SQL Server consulting services for architecture design, Enterprise-to-Standard edition consolidation, Always On Availability Groups, TempDB and storage layout, and T-SQL performance audits. Database engineers review DMV telemetry, Query Store plans, and wait statistics across SQL Server 2016 through 2025 on Windows, Linux, Amazon RDS, and Azure SQL, delivering written runbooks and changes.

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.

  • NDA before access
  • Read-only by default
  • Written scope before work starts

SQL Server version status

Pick the version you run

SQL Server 2022

Mainstream support

Microsoft mainstream support runs through January 2028 and extended support through January 2033, adding Contained Availability Groups and Parameter Sensitive Plan optimization.

Query Store is enabled by default in SQL Server 2022 (compatibility level 160); we validate cardinality estimation changes before raising db compat.

Plan a SQL Server 2022 upgrade

Version lifecycle dates checked against the Microsoft SQL Server lifecycle policy and Amazon RDS support calendar.

Platforms covered
SQL Server 2016 to 2025 on Windows & Linux, Always On AG, Azure SQL MI/DB, and Amazon RDS
Core consulting scopes
Enterprise-to-Standard edition audits, Always On HA design, TempDB & Query Store tuning, and cloud sizing
Support & escalation
Scoped fixed-fee engagements, or 15 minutes P1 response under a 24x7 support agreement. See details

Selected clients

  • Innoviti
  • Blitz
  • Freecharge
  • Nango
  • Recochain
  • Screen Facts
  • Nexora
  • WeCredit

When teams call us

SQL Server architectural and performance problems we solve

Engineering teams bring us in when SQL Server vCore licensing grows faster than traffic, TempDB latch contention stalls writes, Always On failovers misbehave across subnets, or parameter sniffing regressions hit production.

Common SQL Server architectural symptoms, what is usually happening, and where JusDB consultants start
SymptomWhat is usually happeningWhere we start
Enterprise vCore sprawlHigh SQL Server licensing footprint on oversized instancesInstances were provisioned on Enterprise Edition for a single feature or high core count while missing indexes and unparameterized T-SQL drive CPU wait time.Query sys.dm_db_persisted_sku_features and workload CPU/IOPS profiles, tune the top CPU-consuming queries in Query Store, and verify whether Standard Edition + Basic AGs or smaller vCore shapes fit.
PAGELATCH_UP (2:1:1 / 2:1:3)TempDB allocation contention throttles concurrent throughputHeavy #temp table creation, table variables, or RCSI version store activity hits a single TempDB data file or mismatched autogrowth sizes on PFS, GAM, and SGAM pages.Inspect sys.dm_os_waiting_tasks for 2:x:x page latches, configure 8 equally sized TempDB data files on dedicated NVMe storage, and evaluate Memory-Optimized TempDB Metadata.
Always On quorum & split riskMulti-subnet Availability Group failovers time out or drop connectionsWSFC quorum votes lack a File Share or Cloud Witness, RegisterAllProvidersIP is left at 1 without MultiSubnetFailover=True, or synchronous commit runs over high-latency WAN links.Audit cluster node weights, listener DNS TTL and HostRecordTTL, session-timeout settings, and synchronous vs asynchronous secondary commit topologies.
Parameter Sniffing regressionsStored procedures oscillate between sub-second and multi-minute runsAn execution plan compiled for an atypical skewed parameter gets cached and reused for high-cardinality values, triggering key lookup storms or TempDB spills.Compare multiple plan_id entries in sys.query_store_plan, pin the stable plan via sp_query_store_force_plan, and refactor the procedure with targeted indexing or OPTIMIZE FOR.
WRITELOG & PAGEIOLATCH_SHStorage latency bottlenecks transaction commits and buffer readsData files (.mdf/.ndf), transaction logs (.ldf), and TempDB share the same cloud volume or SAN LUN, or excessive VLF fragmentation slows log flushes and crash recovery.Measure stall_ms per file via sys.dm_io_virtual_file_stats, check VLF counts in sys.dm_db_log_info, separate data and log volumes, and right-size max server memory (MB).
Azure SQL / RDS sizing mismatchCloud migration hits DTU/vCore throttling or storage IOPS capsLift-and-shift sizing translated physical cores directly without accounting for Azure SQL Managed Instance log rate limits or RDS EBS gp3 throughput ceilings.Capture a 14-day DMV baseline of log bytes flushed/sec, read/write IOPS, and buffer pool usage to model exact Azure SQL MI, Azure VM, or Amazon RDS instance classes.

How engagements work

How a SQL Server consulting engagement is delivered

Consulting work runs under a written statement of work with clear milestones. For teams that pair consulting with ongoing operational cover, 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.

Four-step SQL Server consulting workflow

  1. Scope

    NDA and written statement of work

    We agree on the target SQL Server instances, architectural goals, and deliverables before any access.

  2. Collect

    Read-only DMV, Query Store, and config snapshot

    Wait stats, file stall metrics, SKU features, and top execution plans gathered with zero production impact.

  3. Deliver

    Ranked written findings with tested T-SQL scripts

    Every recommendation ships with the exact DMV evidence, before/after impact, and rollback script.

  4. Execute

    Guided change window and post-change verification

    We pair with your team during the maintenance window and compare Query Store baselines afterward.

Published initial-response targets when paired with a support agreement

  • 2 to 4 hours

    Business hours

    During covered business hours

  • 15 minutes

    24x7 on-call

    P1 incidents

SeverityInitial responseDefinitionChannel & coverage
P1 · Critical15 minutesProduction database down, primary unreachable, data corruption risk, or active failover event.24x7 on-call (under your service agreement) · Direct PagerDuty, Opsgenie, or phone page plus incident bridge
P2 · High30 minutesSevere latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.24x7 on-call (under your service agreement) · On-call alert plus shared Slack or Teams channel
P3 · Medium60 minutesNon-critical slow query regression, staging issue, backup warning, or replication check alert.24x7 on-call (under your service agreement) · Shared Slack or Teams channel or support ticket
P4 · Low90 minutesConfiguration question, index advisory, planned schema review, or general operational request.24x7 on-call (under your service agreement) · Shared Slack or Teams channel or support ticket

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.

Consulting deliverables

What does SQL Server consulting cover?

Every engagement is scoped around concrete technical outcomes: lower vCore licensing overhead, resilient Always On topologies, tuned TempDB and storage layouts, and verified Query Store execution plans.

  • Enterprise-to-Standard & core consolidation

    We audit feature dependencies and CPU drivers so your team only licenses the SQL Server edition and vCore count the workload actually requires.

    • Audit sys.dm_db_persisted_sku_features and SQL Agent / HA dependencies
    • Right-size vCore allocations by fixing top CPU queries and missing indexes

    sys.dm_db_persisted_sku_features · Query Store · Glenn Berry DMV queries

  • Always On Availability Group architecture

    Design and review of Windows Server Failover Clustering (WSFC) and Linux Pacemaker topologies across local availability zones and DR regions.

    • Synchronous HA replicas, Distributed AGs for cross-region DR, and FCI design
    • Quorum witness design, MultiSubnetFailover listener tuning, and Contained AGs

    Always On AG · WSFC · Pacemaker · Distributed Availability Groups

    SQL Server high availability
  • Wait-stat, Query Store, and T-SQL audit

    Deep forensic review of execution plans, wait statistics, and indexing strategies with tested T-SQL and index changes.

    • CXPACKET, PAGEIOLATCH, WRITELOG, and LCK_M_X wait analysis
    • Parameter sniffing fixes, columnstore design, and MAXDOP / CTFP tuning

    sys.dm_os_wait_stats · Query Store · Extended Events · sp_WhoIsActive

    SQL Server performance tuning
  • TempDB, memory, and storage layout

    Storage and memory architecture aligned with Microsoft SQL Server best practices for bare-metal, VMware, AWS EC2, and Azure VMs.

    • TempDB file layout (8 equal files), autogrowth sizing, and metadata optimization
    • Separate data, log, and TempDB volumes with 64 KB NTFS allocation units

    sys.dm_io_virtual_file_stats · sys.dm_db_log_info · Lock Pages in Memory

  • Cloud sizing & migration blueprints

    Evidence-backed target architecture for moving on-premises SQL Server to Azure SQL Managed Instance, Azure VMs, Amazon RDS, or PostgreSQL.

    • Log write-rate and IOPS modeling for Azure SQL MI vs SQL Server on VMs
    • Cutover runbooks using Distributed AGs, Log Shipping, or native S3 backups

    Azure Migrate · AWS DMS · dbatools · Babelfish assessment

    SQL Server migration services
  • Backup, RPO/RTO, and security review

    Review of maintenance jobs, corruption checks, encryption, and least-privilege access controls against your recovery and audit requirements.

    • Ola Hallengren DatabaseBackup, IndexOptimize, and DBCC CHECKDB validation
    • Transparent Data Encryption (TDE) certificate lifecycle and SQL Audit review

    Ola Hallengren MaintenanceSolution · TDE · SQL Server Audit

    SQL Server remote DBA

Consolidation and written evidence

How tuning wait stats unlocks vCore consolidation

Before renewing a SQL Server Enterprise agreement or sizing Azure SQL Managed Instance, we eliminate the query and TempDB bottlenecks inflating CPU utilization.

From sprawled Enterprise vCores to a right-sized Always On topology

Select a stage to see how storage, TempDB, and HA architecture evolve.

Application connection string and AG Listener

Application hits a single oversized Enterprise instance where unindexed queries and TempDB contention consume 70% CPU.

32 vCores Enterprise · High CPU wait
  • Primary (32 vCore Enterprise)

    Carries OLTP + reporting + unindexed scans

    CPU 78% · CXPACKET & PAGELATCH waits

  • TempDB (Single .mdf file)

    Shares OS/data disk with 10% percent autogrowth

    PAGELATCH_UP on 2:1:1 PFS page

  • DR Replica (Manual backup copy)

    Nightly full backup with untested restore time

    RPO up to 24h · Untested RTO

Many SQL Server estates pay for extra Enterprise vCores to mask missing composite indexes, MAXDOP=0 defaults, and single-file TempDB contention.

Example written finding from a SQL Server consulting auditSample deliverable

1. DMV check for Enterprise-only features and TempDB page latch waits

-- Check if any database uses Enterprise-only persisted features
SELECT DB_NAME() AS database_name, feature_name, feature_id
FROM sys.dm_db_persisted_sku_features;

-- Inspect active TempDB PAGELATCH contention on PFS/GAM/SGAM (2:x:x)
SELECT session_id, wait_type, wait_duration_ms, resource_description
FROM sys.dm_os_waiting_tasks
WHERE wait_type LIKE 'PAGELATCH%' AND resource_description LIKE '2:%';

2. Equal-sized 8-file TempDB layout & server parallelism baseline

-- Standardize 8 equally sized TempDB data files with fixed growth
ALTER DATABASE [tempdb] MODIFY FILE (NAME = N'tempdev', SIZE = 16384MB, FILEGROWTH = 1024MB);
-- Add tempdev2..tempdev8 at 16384MB each on dedicated NVMe volume

EXEC sys.sp_configure N'cost threshold for parallelism', 50;
EXEC sys.sp_configure N'max degree of parallelism', 8;
RECONFIGURE WITH OVERRIDE;

Finding

Zero persisted Enterprise SKU features used; single TempDB file and MAXDOP=0 drove 68% of CPU waits

Auditing sys.dm_db_persisted_sku_features across all 14 user databases returned zero rows. Meanwhile, CXPACKET and PAGELATCH_UP on 2:1:1 accounted for 68% of non-idle wait time because MAXDOP was left at 0 and TempDB ran on a single data file.

Instance vCore footprint32 → 16 vCores
Peak TempDB latch wait185ms → < 1ms

Your team and ours

What managed SQL Server cloud services still leave 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 cloud service versus your own servers
AreaManaged cloud (Azure SQL MI/DB, Amazon RDS)Windows / Linux VMs or bare metal
Host OS, storage attach, and hypervisor availabilityAmazon RDS and Azure SQL Managed Instance run the underlying host.Your infrastructure team, with JusDB sizing volumes, NTFS block size, and cluster quorum.
Query Store plans, missing indexes, and T-SQL regressionsYours. Managed SQL Server instances execute your T-SQL as written and do not refactor stored procedures.Analyzed and tuned by JusDB in a written consulting engagement.
TempDB file layout, MAXDOP, and memory configurationPartially defaulted by the cloud provider, but MAXDOP, Cost Threshold for Parallelism, and TempDB sizing still require workload tuning.Configured to Microsoft best practices (8 equal TempDB files, Lock Pages in Memory, max server memory).
Enterprise vs Standard Edition licensing optimizationCloud providers bill per vCore and edition you select; they do not audit whether your schema actually uses Enterprise features.JusDB audits SKU features, tunes CPU consumption, and delivers a right-sizing blueprint.
SQL Server 2016 EOL and 2022 / 2025 upgrade architectureAmazon RDS ended SQL Server 2016 support in July 2026 and forces upgrades to 2019; major version testing remains your responsibility.JusDB designs side-by-side Distributed AG or Log Shipping cutovers with compatibility level testing.

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 consulting scope

  • 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

Where your SQL Server runs

Compare options

How JusDB SQL Server Consulting compares with generalist agencies and hiring

Compare a scoped JusDB SQL Server architecture and tuning engagement against generalist IT consultancies, cloud provider advisories, or hiring full-time senior DBAs.

Evaluation Vector
JusDB DBRE
In-House DBALegacy AgencyDeveloper Generalist
Always On Availability Group ArchitectureMulti-subnet WSFC cluster design, synchronous and asynchronous commit balancing, quorum witness optimization (Cloud/File Share), and automated failover verification.Basic single-subnet setup vulnerable to split-brain, lease timeout stalls, and unmonitored redo queue latency on secondaries.Generic template AG deployments without log throughput sizing, synchronous HADR_SYNC_COMMIT latency modeling, or cross-datacenter DR.Attempts application-level failover or manual connection string swapping without WSFC quorum fencing, causing extended outages.
TempDB Allocation & Latency TuningProportional fill calibration, equal file sizing matched to logical cores/NUMA nodes, trace flags 1117/1118, and memory-optimized table variable acceleration.Single TempDB file or arbitrary counts on shared OS storage, causing severe PAGELATCH_UP waits on PFS, GAM, and SGAM allocation bitmaps.Applies outdated 'one file per core' rules blindly across high-core systems, multiplying file allocation latch contention and checkpoint overhead.Treats TempDB like a standard user database, creating uncontrolled #temp tables inside nested loops that saturate shared storage IOPS.
Query Store Plan Regression ForensicsAutomated regression capture, forced plan stabilization, parameter sniffing eradication (OPTIMIZE FOR UNKNOWN), and Intelligent Query Processing telemetry.Manual, reactive plan inspection after production alerts fire; struggles with plan cache bloat and parameter sensitivity issues.Relies on heavy SQL Profiler and server traces that add 15%+ CPU overhead and miss historical plan transitions.Leaves Query Store disabled or at default retention; resorts to clearing the entire plan cache with DBCC FREEPROCCACHE during slowdowns.
NUMA & MAXDOP Memory ErgonomicsSoft-NUMA partition mapping, MAXDOP calibration per socket, Cost Threshold for Parallelism (CTFP) right-sizing, and Buffer Pool / LPIM governance.Default MAXDOP 0 or arbitrary instance caps without NUMA boundary awareness, causing cross-node foreign memory access and scheduler stalls.Applies static legacy rules across high-core virtualized hypervisors, causing CXPACKET thread exhaustion and coordinator bottlenecking.Leaves max server memory unconfigured, allowing SQL Server to starve the host OS and trigger destructive Windows paging file swapping.
Disaster Recovery & RPO/RTO ValidationContinuous tail-log backup orchestration, automated CHECKSUM restore verification drills, point-in-time recovery (PITR) auditing, and restore timing tested against your RTO target.Nightly native backup jobs without automated checksum validation or regularly tested multi-terabyte disaster recovery restore drills.Relies on hypervisor VM snapshots that break SQL Server transaction log LSN chains and invalidate point-in-time database restoration.Unscheduled manual SQL dumps stored on the local database volume, risking total permanent data loss during drive failures.
Enterprise Security & TDE EncryptionTransparent Data Encryption (TDE) with external Azure Key Vault / EKM, Always Encrypted with secure enclaves, granular RBAC, and SOC 2 / ISO 27001 audit logging.Native TDE with database master keys stored locally on the same instance without centralized key lifecycle or rotation protocols.Shared 'sa' credentials, unencrypted TLS TDS endpoints, and overly broad sysadmin memberships assigned across development teams.Hardcoded plaintext database credentials in application configs communicating over unencrypted public IP addresses.

For procurement and security

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

We work alongside your application and infrastructure teams. Your team approves production changes and keeps every DMV audit script, architecture diagram, and runbook.Raguraman, Engineering Manager · Allen D, Lead Database SRE
  • Mutual NDA
  • Written statement of work
  • Named engineers
  • Least-privilege access
  • NDA before access

    Signed before any diagnostic access. The initial scoping call needs no database credentials.

  • Written agreement

    Target SQL Server instances, deliverables, timeline, and fees agreed in writing before work starts.

  • Least-privilege accounts

    VIEW SERVER STATE and read-only access by default, connected through your bastion or VPN.

  • Deliverables you keep

    Every DMV diagnostic query, T-SQL script, and runbook stays with your team. Meet the JusDB team.

JusDB's security practices are aligned with ISO 27001 and SOC 2 Type II, and JusDB is pursuing both certifications (see Terms, section 12). Read the stated status.

FAQ

Common SQL Server consulting questions

Answers on Enterprise-to-Standard consolidation, Always On Availability Groups, DMV audits, and SQL Server 2016 End of Life upgrades.

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)

What does a SQL Server consulting engagement include?

A SQL Server consulting engagement starts with a read-only DMV, Query Store, and configuration audit of your instances. We deliver a written report ranked by impact, complete with exact T-SQL scripts, index definitions, TempDB and memory settings, and architecture diagrams, and can implement the approved changes with your team.

Can you help consolidate SQL Server Enterprise Edition to Standard Edition or fewer vCores?

Yes. We inspect sys.dm_db_persisted_sku_features, availability group topology, and SQL Agent jobs across every database, then tune the top CPU-consuming queries in Query Store so you can safely reduce vCore counts or move eligible workloads to SQL Server Standard Edition.

Which SQL Server versions and platforms do you cover?

We consult on SQL Server 2014, 2016, 2017, 2019, 2022, and 2025 running on Windows Server and Linux (RHEL, Ubuntu, SLES), as well as Amazon RDS for SQL Server, Azure SQL Managed Instance, Azure SQL Database, and Google Cloud SQL for SQL Server.

How do you diagnose SQL Server performance bottlenecks without impacting production?

We read existing DMV cumulative counters (sys.dm_os_wait_stats, sys.dm_io_virtual_file_stats, sys.dm_exec_query_stats), Query Store history, and the lightweight system_health Extended Events session. We never run heavy Profiler traces against production.

Can you design or audit our Always On Availability Group topology?

Yes. We review Windows Server Failover Clustering (WSFC) or Linux Pacemaker quorum votes, synchronous vs asynchronous commit modes, MultiSubnetFailover listener settings, and read-only routing lists, and we run rehearsed failover drills to verify your actual RTO and RPO.

Do you assist with SQL Server 2016 End of Life upgrades and cloud migrations?

Yes. SQL Server 2016 reached End of Extended Support on 14 July 2026. We design and execute low-downtime migrations to SQL Server 2022 or 2025 on Windows/Linux VMs, Azure SQL Managed Instance, or Amazon RDS using Distributed Availability Groups, Log Shipping, or native backup/restore.

What are your response targets if we also need ongoing SQL Server support?

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. 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.

When should we choose SQL Server Consulting versus SQL Server Remote DBA or Support?

Choose SQL Server Consulting for a fixed-scope project such as an architecture review, a licensing and vCore consolidation assessment, a performance audit, or a version upgrade. Choose SQL Server Remote DBA for ongoing weekly maintenance, Ola Hallengren automation, and schema changes, or SQL Server Support for agreed P1-P4 incident response.

SQL Server playbooks and comparisons

SQL Server maintenance, cloud sizing, and migration guides

Practical engineering guides on Ola Hallengren maintenance automation, Azure SQL Managed Instance vs Azure VMs, and Amazon RDS migrations.

Next step

Talk to a SQL Server engineer about your architecture

Tell us which SQL Server editions, versions, and cloud platforms you run and what you want reviewed. 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 · written scope first

Explore all SQL Server services

Need a different SQL Server service? Browse our complete offerings.