You are running a version that stopped getting fixes
SQL Server 2014 went end of support in July 2024, and 2016 is not far behind. No more security patches, and auditors notice.
Moved to a supported release
Running SQL Server?
Most SQL Server instances that land on our desk have been there for a decade, patched by whoever happened to be around, and nobody wants to be the one who moves them. We work out what the application actually depends on and get the database onto something still supported, without the business standing still for a week.
What it is
Microsoft SQL Server is a relational database first released in 1989, originally co-developed with Sybase. It has grown into an enterprise RDBMS that quietly underpins countless line-of-business applications, from ERP and accounting systems to warehouse, scheduling and clinical software.
It ships in tiers. Express is free with a 10 GB database cap, then Web, Standard and Enterprise step up on features and price. It traditionally ran only on Windows Server, but from the 2017 release it also runs on Linux and in containers, which has opened up where it can live.
The honest version
No technology is all upside. This is where Microsoft SQL Server earns its place and where it tends to cause trouble.
Sound familiar?
The Microsoft SQL Server problems that bring people to us, and what you have once each one is fixed.
SQL Server 2014 went end of support in July 2024, and 2016 is not far behind. No more security patches, and auditors notice.
Moved to a supported release
Two procedures touch the same tables in a different order, usually a report colliding with a load, and one of them loses every night.
Deadlocks traced and removed
Full recovery model with no log backups running, or a replication job that has been stuck for days holding the log open.
Log backups scheduled, size reclaimed
Jobs, logins, linked servers and SSIS packages that nobody has documented, and a sysadmin password on a sticky note somewhere.
Owned, documented, handed over
A reporting query that scans a 400 million row table because the useful index was dropped in 2019 and never put back.
Indexed, with Query Store watching
A service account expired in Active Directory, or SQL authentication was turned off during a hardening pass without telling anyone.
Auth sorted, with an audit trail
A maintenance plan writing to a drive that filled last month, so the last known-good backup is older than anyone is comfortable with.
Backups verified, restores tested
Two databases built years apart on different defaults, now being joined in one query and refusing to compare their text columns.
Collation resolved across the estate
What we do
Hand us one stuck instance, or your whole SQL estate.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
It is no longer getting security fixes from Microsoft, since extended support ended in July 2024. It will keep working, but any new vulnerability stays open, and most compliance frameworks treat it as a finding. The sensible path is a planned upgrade to 2019 or 2022, or a move to a managed cloud instance, rehearsed against a copy of the live data first.
Enterprise is sold per core, in two-core packs, and list price has hovered near fourteen thousand US dollars per core before Software Assurance. For a modern dual-socket server the bill reaches six figures quickly. We often find clients are paying Enterprise when Standard would carry their workload, or paying per core when a Managed Instance would land cheaper. It is worth a licence review before any renewal.
Often, yes, especially where the Enterprise bill is the main pain. We look at stored procedures, SSIS packages, linked servers and anything that leans on T-SQL only features, then give you an honest estimate of the effort. Some applications port over in weeks. Others are so tied to SQL Server that staying on it, perhaps on a cheaper tier, is the better answer.
Usually it is a handful of queries doing far more work than they should, because an index is missing, statistics are stale, or a plan has regressed since the last data load. Beyond that, under-sized memory, misconfigured tempdb, and blocking from long-running transactions show up repeatedly. Query Store and wait statistics tell the real story once we look.
Yes, and this is a regular job for us. We inventory the instance, map out logins, jobs, maintenance plans, SSIS packages and linked servers, rotate the credentials that need rotating, and write down what was never written down. You end up with a database you understand and a team to call when it misbehaves.
Either works from the 2017 release onward. Linux can cut Windows Server licence costs and fits a container workflow well. Windows still makes sense when the surrounding estate is Active Directory heavy or the application has Windows-only dependencies. We help pick based on what the rest of your stack looks like, not on a preference.
Estimates do not cost anything. Tell us the version, the symptoms and roughly the size, and you get a fixed price before we touch the instance.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: