SQL Server

SQL Server is the database you’re already paying for.

Almost nobody adopts it deliberately for a web application. It’s there because the business runs on Microsoft, or because a piece of commercial software brought it along, or because a decision made a decade ago is still renewing in the background. It is an excellent database. It is also the only one in common use where the invoice arrives whether you think about it or not.

Which makes the useful questions here financial rather than technical. The technology is rarely the problem. The commercial model is where businesses get caught, and it catches them at exactly the moment things are going well.

“It’s enterprise-grade and already integrated”

You’ll be told SQL Server is enterprise-grade, thoroughly supported, and already integrated with everything else you run.

All true. None of it is the part that will surprise you.

Why scaling up your SQL Server bill happens twice

Scaling up costs you twice. SQL Server is licensed per core. When an application gets busier, the ordinary engineering response is a bigger server, and a bigger server means more cores. So the hosting bill rises, and the licence bill rises with it, in a way nobody flags at the point of approving the change. If you take one thing from this page: before you sign off more capacity, ask what it does to licensing, not just to infrastructure. That question is rarely asked and the answer is occasionally shocking.

The Express and Developer edition trap

The free editions have real limits, and people forget they’re on them. Express and Developer editions cost nothing but cap database size and memory. Systems get built on Express, grow, and hit a ceiling that arrives as a mysterious performance problem rather than an obvious licensing one. Developer edition is free but not licensed for production, which is a compliance issue rather than a technical one and tends to be discovered during due diligence.

The weakness is the price, not the product

The weakness is cost, not capability. It’s worth being clear about this, because it’s easy to read scepticism about the price as scepticism about the product. SQL Server does its job extremely well and has support timelines you can plan a decade around. That predictability is exactly what you’re buying with the licence fee, and for many businesses it’s a fair trade.

What you pay for if you’re not a Microsoft business

If nothing else in your business is Microsoft, you’re paying for an ecosystem you aren’t using. It runs on Linux and in containers now, but the tooling, the hiring assumptions and the operational habits all assume a Microsoft estate. The value of SQL Server compounds with Active Directory, Power BI and the rest. On its own, in an otherwise non-Microsoft business, much of what you’re paying for sits idle.

What it costs to leave: T-SQL and stored procedures

And leaving is expensive. Of the common databases this is the hardest to move away from, because T-SQL, stored procedures and SQL-Server-specific tooling don’t port directly, and in most businesses a decade of logic has accumulated inside the database rather than in the application. Treat a migration as a project with a business case, not a switch to flip.

Questions to ask before you approve more capacity

• “What would doubling our capacity cost in licensing?” Ask before approving the capacity, not after.
• “Which edition are we running, in production, right now?” Then ask whether it’s licensed for that.
• “How much of our business logic lives in stored procedures rather than in the application?” This is the number that determines what leaving would cost, and most businesses have never counted it.
• “What are we using that’s specific to SQL Server?” If the honest answer is very little, you’re paying a premium for compatibility you don’t need.

When SQL Server earns its licence fee

When your business runs on Microsoft top to bottom. If you have Windows Server, Active Directory, .NET applications and Power BI reporting, SQL Server sits in the middle of all of it and the integration is worth real money. Pulling it out to save licence fees would cost more than it saves.

When commercial software you depend on requires it. ERP, accounting and HR systems frequently mandate SQL Server, and that’s not a fight worth having for the sake of the database underneath.

When predictability is worth paying for. Published support lifecycles stretching years ahead, a single accountable vendor, and a large partner ecosystem are real things to buy. Regulated businesses in particular are often purchasing the support relationship as much as the software.

When SQL Server is the wrong database to stay on

For a new web application, when nothing else in the business is Microsoft. PostgreSQL and MySQL cover the same ground for that workload with no licence line at all, and the money is better spent on the application.

When it’s being kept because moving is hard. That’s a real reason to stay this year and a poor reason to stay indefinitely. If the honest answer to “why SQL Server?” is that nobody wants to unpick the stored procedures, you don’t have a database strategy, you have a debt. Worth knowing the size of it even if you never pay it down.

When you’re on a free edition and growing. That runway ends. Better to find out where the limit is now than during your busiest week.