Databases Compared
SQL Server: The Enterprise Database for Microsoft Estates
SQL Server is Microsoft's enterprise relational database: T-SQL instead of PL/SQL, Always On availability groups for HA, and a licensing model that prices it like Oracle rather than like MySQL. It runs on Windows and, since 2017, on Linux, and it is the natural database choice where the estate around it is Microsoft. This article covers what running it well costs in discipline and money.
Key points
- The engine's enterprise surface is real: columnstore indexes for analytics, In-Memory OLTP, Query Store for plan regression troubleshooting, and availability groups (readable replicas plus automatic failover) for HA; the features exist and are mature.
- Licensing is the contract: per-core pricing with Software Assurance on the enterprise tier, edition tiers (Express free, Web, Standard, Enterprise) that gate features as much as capacity; audits behave like Oracle's, so environment definitions and virtualization rules belong in writing before purchase.
- HA discipline: Always On availability groups within Windows Server Failover Clustering or standalone; backups remain separate duty (full/diff/transaction-log chains with tested point-in-time restore); maintenance plans without verification are theater.
- Operations surround the database: SQL Agent for scheduling, SSMS/ADS for management, Extended Events plus Query Store for performance work; performance problems live mostly in plans and blocking (wait statistics), not in memory settings.
- Cross-platform reality: SQL Server on Linux supports the core engine (with some feature gaps such as certain third-party integrations), and containerized instances carry dev/test workflows; production sizing still favors dedicated infrastructure.
- Where it fits among our database articles: .NET estates with AD-backed identity and T-SQL-skilled staff get a coherent stack; greenfield Linux estates compare TCP-on-postgres and Oracle-grade options in our postgresql and oracle articles; pricing the license before the features is the practical rule.
Field note
The most expensive SQL Server problem we diagnosed was not performance, it was a licensing audit: a Standard edition instance had quietly grown onto hardware that violated the virtualization terms. The fix cost less than the negotiation. Price the license before the schema.
Frequently asked questions
Is SQL Server cheaper than Oracle?
Usually in comparable tiers, but both are enterprise-lottery priced per core with option add-ons. The honest comparison is workload-specific: features you actually use versus licenses and Software Assurance over three years.
Can I run it on Linux?
Yes, the core engine and the principal HA features run on Linux; check feature parity per version against your workload (some SSIS/SSRS adjacent tooling differs) before committing.
What is the maintenance plan discipline?
Backups on tested chains with point-in-time verification, index and statistics maintenance sized by fragmentation thresholds (not blanket rebuilds), and monitoring for blocking and wait stats; every script needs an owner.
How does SQL Server compare with PostgreSQL for a new project?
If the team knows T-SQL and the estate is Microsoft, SQL Server's tooling is cohesive. For open-ecosystem licensing freedom and extension surface, our postgresql article covers the alternative; the deciding factor is usually the staff's existing SQL dialect fluency.
How Kinetikatech helps with databases compared
Here's the deal: Database engine choices for hosting workloads, compared on correctness guarantees, operational weight, and real cost: embedded engines against servers, MySQL against PostgreSQL, SQL against document stores, plus the legacy case study that keeps coming back. Hand it to our Server Management and Website Speed Optimization service and it's covered, assessed properly, implemented cleanly, monitored around the clock.