Running SQL Server?

SQL Server stuck on an old version? We fix it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

ERRORLOG

still failing

What it is

Microsoft SQL Server at a glance

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.

Type
Relational database
First released
1989
License
Proprietary, free Express tier
Maintained by
Microsoft Corporation
Typically used for
Line-of-business apps, ERP, data warehousing, .NET back ends

The honest version

Microsoft SQL Server pros and cons

No technology is all upside. This is where Microsoft SQL Server earns its place and where it tends to cause trouble.

Where Microsoft SQL Server is strong

  • Industrial-grade reliabilityBackup, restore, Always On availability groups and point-in-time recovery are mature and well documented. When it is set up properly, it stays up.
  • The tooling is excellentSQL Server Management Studio, Extended Events, Query Store and the Profiler give you a clearer view of what the database is doing than almost anything else in this category.
  • It fits the Microsoft stackDeep integration with .NET, Active Directory and Windows Server means fewer moving parts to glue together on a Microsoft shop floor.
  • Heavy workloads have a homeColumnstore indexes and in-memory OLTP let it chew through reporting and high-throughput transactional work that would strain a general-purpose setup.
  • SSRS and SSIS come in the boxReporting Services and Integration Services ship alongside the engine, so dashboards and overnight data loads do not need a separate product.

Where Microsoft SQL Server bites

  • Licensing is not cheapEnterprise is priced per core and the bill climbs quickly on modern CPUs. Feature gating between Express, Standard and Enterprise can force an upgrade just to get one capability.
  • Historically tied to WindowsLinux support arrived in 2017, but a lot of installed instances still live on Windows Server, which carries its own licence and patching schedule.
  • Old versions lingerInstances running 2008, 2012 and 2014 are still common in the wild, long past end of support, because the application on top has never been retested.
  • The side services driftSSIS packages and SSRS reports are their own little worlds, often built by someone who has left, and they break quietly when the engine underneath moves.
  • Upgrades need rehearsalCompatibility levels, deprecated features and collation changes can bite an application that has not been exercised against the new version.

Sound familiar?

Common Microsoft SQL Server problems we fix

The Microsoft SQL Server problems that bring people to us, and what you have once each one is fixed.

version: 12.0.6024.0 (SQL 2014)

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

deadlocked on lock resources

Overnight jobs deadlock each other

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

transaction log for database 'X' is full

The log drive fills and writes stop

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

last DBA: left in 2021

The person who built it is long gone

Jobs, logins, linked servers and SSIS packages that nobody has documented, and a sysadmin password on a sticky note somewhere.

Owned, documented, handed over

CPU 98% · PAGEIOLATCH waits

The database is slow at month-end

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

Login failed for user 'sa'

An app server cannot log in any more

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

Backup failed: 3041

Backups have been failing quietly

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

collation conflict

A merge or upgrade throws collation errors

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

SQL Server help, from end-of-support upgrades to day-to-day care

Hand us one stuck instance, or your whole SQL estate.

End-of-support upgrades
Moving 2012, 2014 or 2016 instances onto a supported release, rehearsed against a copy of your data before anything real moves.
Performance
Query Store analysis, index work, wait statistics and memory settings, with timings captured before and after so the change is visible.
Inherited instances
Taking over a database whose DBA has moved on. Logins, jobs, SSIS, linked servers, backups, all mapped out and brought back under control.
Backup and recovery
Full, differential and log backups that actually run, off-server copies, and a restore that has been practiced on a schedule.
High availability
Always On availability groups, log shipping or failover clusters, sized to what the business can tolerate when something breaks.
Moving off
Lift-and-shift to Azure SQL or Managed Instance, or a measured migration onto PostgreSQL where the licence bill no longer makes sense.
Managed Tech
Patching, monitoring, index and backup upkeep, with a US engineer to call when something looks wrong.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Microsoft SQL Server alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Microsoft SQL Server questions

Something else? Call+1 737 727 7327

Is SQL Server 2014 still safe to run?

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.

How much does SQL Server Enterprise cost?

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.

Can we move off SQL Server to PostgreSQL?

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.

Why is my SQL Server database slow?

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.

Can you take over a SQL Server database from an ex-DBA?

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.

Should we run SQL Server on Linux or Windows?

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.

How much does SQL Server help cost?

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

SQL Server giving you grief?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.