SQL Server is the highest exposure server product in most enterprise estates. The unit prices on Enterprise edition are large, the virtualization rules are unforgiving, the Software Assurance attach drives the available rights, and the audit math is mechanical. Most enterprises run SQL Server in configurations that were once compliant and quietly are not today because the environment moved, the cluster spread, or the virtualization platform changed underneath. SQL Server reconciliation is the single most material activity in any Microsoft compliance review.
SQL Server is sold in two editions for enterprise deployment. Enterprise and Standard. Each is licensable under the Per Core model or the Server plus CAL model. The decision is structural. The wrong choice is usually invisible until the auditor models the alternative.
The full database platform. Unlimited virtualization with Software Assurance on Enterprise per core. Advanced high availability, in memory features, advanced analytics, transparent data encryption at scale. Priced by physical core or virtual core depending on the deployment model.
The mid tier database platform. Sufficient for most departmental, line of business, and reporting databases. Per Core or Server plus CAL. The Server plus CAL model is the cheaper path where the named user or device count is small relative to the core count.
SQL Server virtualization is governed by two strict rules. License the host or license the VM. License Mobility requires active Software Assurance. License reassignment within ninety days is constrained. The virtualization model is where most SQL audit exposure originates because the platform team and the licensing team rarely talk to each other.
License the vCPUs assigned to each SQL VM. Minimum four cores per VM regardless of allocation. Cheapest model where the SQL footprint is small and the rest of the cluster runs other workloads. The right answer for the majority of mid sized SQL estates.
License the full host on Enterprise per core with Software Assurance. Unlimited VMs of SQL Server on that host. The right answer for dense SQL clusters where the VM count justifies the host level economics. Most large enterprise SQL deployments belong here.
Software Assurance grants passive failover rights for SQL Server. A second instance running in passive mode does not require licensing while SA is active. The benefit was expanded in 2019 and clarified again in 2022. Most enterprises license passive secondaries unnecessarily because the SA benefit was never operationalized.
SQL Server audit findings have a consistent shape. Enterprise edition deployed where Standard was licensed. Virtualization spread without License Mobility. Development instances counted as production. SQL Server Express deployed at scale and audited as Standard. The settlement math runs large because the unit prices on Enterprise per core are unforgiving.
Database administrators enable transparent data encryption, partitioning, online indexing, or any of two dozen Enterprise only features without realizing the feature flips the license requirement from Standard to Enterprise for the instance. The audit query that surfaces this is well established and produces a finding in most enterprises that run a mixed edition estate.
The defense is procedural. Feature governance at the database level. Pre audit reconciliation of feature usage to license edition per instance. The remediation is feature removal or license upgrade before the audit data lands on the auditor's spreadsheet.
The most expensive SQL audit finding in the modern era. SQL VMs configured for vMotion or Live Migration across a cluster where only a subset of hosts are licensed for SQL host level. Every host the VM has run on in the trailing ninety days requires licensing. The auditor pulls the vCenter or System Center logs and aggregates the host inventory the VM has touched.
The defense is platform configuration. SQL VMs pinned to licensed hosts with affinity rules. Software Assurance attached to enable License Mobility across the broader cluster. Pre audit reconciliation of VM movement against host license inventory. The settlement on this pattern is typically the largest line in a SQL audit finding.
SQL Server is the highest dollar line on most server renewals and it is consistently the line with the most concession headroom. The right preparation produces a meaningful discount on the renewed core count and protects the edition mix through the term.
The renewal moment is the right time to reconcile the SQL core count to actual production utilization, the edition mix to actual feature usage, and the virtualization model to the actual cluster topology. The buyer who arrives at the table with the reconciliation produces a meaningfully smaller core count and a meaningfully cheaper renewed envelope.
The SQL line is part of the broader EA renewal envelope. The right size moves the renewal number without changing what the database team can deploy.
Software Assurance on SQL Server pays for itself only where the buyer actually uses the rights. License Mobility for cluster movement, passive DR rights, step up to Enterprise, and version upgrades. The renewal is the moment to attach SA to the cores that need the rights and remove SA from the cores that do not.
Contract drafting protects the position. Capped uplift on the per core price. Pre approved expansion at contracted rates through the term. Clarification language on virtualization rights. The right to step between editions without repurchase. The buyer keeps optionality and the SQL line tracks the real estate rather than the historical one.
The SQL engagement is a per instance reconciliation, an edition versus feature usage review, a virtualization model decision per cluster, and a Software Assurance attach optimization. The output is a SQL footprint that defends the audit and prices the renewal to actual production consumption.
We pull the SQL inventory across the estate. Production, non production, development, test, reporting, ETL, embedded. Each instance is reconciled to edition, license model, host topology, and feature usage. The output is a defensible SQL position per instance with the cores that should be licensed, the edition that should be deployed, and the Software Assurance that should be attached.
The same reconciliation surfaces the audit exposure that the buyer carries unknowingly. Enterprise features on Standard instances. SQL Express running where Standard is the actual fit. Virtualization spread that breaks License Mobility. Each finding is remediated before the auditor finds it.
We model the SQL renewal envelope against the reconciled inventory, the consumption baseline, and the concession data from comparable enterprise SQL renewals signed in the trailing twelve months. The output is a defensible renewal number that anchors the negotiation and a contract that protects the position through the term.
The contract drafting covers capped uplift on the SQL per core line, pre approved population expansion at contracted rates, clarification of virtualization rights, edition step up flexibility, and DR benefit language that operationalizes the Software Assurance entitlement. The SQL line becomes a predictable cost rather than a recurring audit risk.
The SQL diagnostic surfaces edition drift, virtualization spread, missed DR benefit, and Software Assurance attach decisions that no longer reflect the estate. The result is a clean compliance baseline and a meaningfully smaller per core envelope into the next renewal.