Which SQL Server versions do you upgrade from and to?

We upgrade from any supported or end-of-life SQL Server version (2008 and later) to the latest SQL Server 2022, Azure SQL Database, or Azure SQL Managed Instance.

How do you handle query plan regressions?

We use Query Store, Database Experimentation Assistant, and compatibility level testing to identify and resolve query regressions before they impact production.

How long does a typical upgrade take?

Planning and testing typically takes 2-4 weeks. The actual upgrade cutover is usually completed within a maintenance window of 2-6 hours depending on database size.

Version Upgrades Done Right

SQL Server Upgrades Modern Features, Zero Surprises

Last updated: January 18, 2026

Running an older SQL Server version? Upgrades unlock better performance, enhanced security, and new features—but only if done correctly. We plan and execute upgrades that work the first time.

Plan Your Upgrade See How It Works

Why Upgrades Get Delayed

Most organisations know they should upgrade. These concerns hold them back.

Fear of Breaking Things

Applications that work today might break tomorrow. Query plans change, deprecated features disappear, and subtle incompatibilities emerge.

Downtime Requirements

Traditional upgrades require extended maintenance windows that modern businesses can't afford.

Security Pressure

Older versions lose support and stop receiving security patches, creating compliance and risk issues.

End of Support Costs

Extended Security Updates for out-of-support versions are expensive. Upgrading is often cheaper than staying put.

Missing Modern Features

Query Store, Intelligent Query Processing, and other game-changing features are only available in newer versions.

Internal Expertise Gaps

Your team hasn't upgraded before. The complexity and risk make it tempting to keep postponing indefinitely.

Our Approach

A systematic methodology that delivers consistent, measurable results.

Compatibility Assessment

We analyse your databases and applications for upgrade blockers and develop a remediation plan.

Data Migration Assistant analysis
Query Store baseline capture
Deprecated feature identification
Application compatibility testing

Upgrade Strategy

We design the right upgrade approach for your environment—in-place, side-by-side, or hybrid.

Upgrade path selection
High availability planning
Rollback strategy
Downtime minimisation

Execution & Validation

We execute the upgrade, validate functionality, and ensure performance meets or exceeds pre-upgrade levels.

Controlled upgrade execution
Query plan regression testing
Performance validation
Post-upgrade optimisation

How It Works

A clear, proven process from initial assessment to ongoing support.

Assessment

We analyse your current environment, run compatibility tools, and identify any blockers or required changes.

1 week

Planning

We design the upgrade strategy, create detailed runbooks, and establish success criteria and rollback triggers.

1 week

Testing

We perform test upgrades in non-production, validate application functionality, and capture performance baselines.

2-3 weeks

Production Upgrade

We execute the production upgrade during your approved window with monitoring and rollback readiness.

Varies

Stabilisation

We monitor post-upgrade, address any query plan regressions, and tune the new version for optimal performance.

1-2 weeks

Results You Can Measure

Real improvements from real client engagements.

100%

Upgrade Success Rate

No failed production upgrades

30%

Avg. Performance Gain

From modern query optimizer

< 2 Hours

Typical Downtime

With proper planning

2012→2022

All Versions Supported

Including multi-version jumps

Frequently Asked Questions

Can we skip versions (e.g., 2012 to 2022)?

Yes. SQL Server supports direct upgrades from 2012 and later to 2022. We'll assess your specific situation and recommend the best path, which might include intermediate steps for complex environments.

What about compatibility level?

We typically upgrade with the database compatibility level unchanged initially, then raise it after validating application behaviour. This gives you new engine features while minimising query plan changes.

How do you handle Always On Availability Groups?

We use rolling upgrades—upgrading secondary replicas first, failing over, then upgrading the former primary. This approach minimises downtime to seconds for the failover.

What if queries run slower after the upgrade?

We capture query performance baselines before upgrading. Post-upgrade, we compare performance and address any regressions using Query Store, plan guides, or compatibility level adjustments.

Do you handle the Windows Server upgrade too?

Yes, we can coordinate SQL Server upgrades with Windows Server upgrades. Often these are done together as part of a broader infrastructure modernisation project.

What about SQL Server licensing?

We can advise on licensing implications and help you understand options like Software Assurance, license mobility, and Azure Hybrid Benefit. For formal licensing decisions, we recommend consulting with Microsoft or a licensing specialist.

Ready to Get Started?

Schedule a free consultation to discuss your database challenges. We'll review your environment and provide actionable recommendations.

Schedule Free Consultation View Pricing