MICROSOFT LICENSING · MODULE 6 · SQL SERVER
SQL Server licensing:
Server/CAL or per core?
SQL Server stores the data behind many business applications. This straightforward guide explains when Standard is enough, when Enterprise is useful, when users are counted, and when physical or virtual cores must be licensed.
The short answer
Standard offers two licensing models. Enterprise is generally licensed per core.
SQL Server Standard can be purchased with a server licence plus SQL CALs for the users or devices accessing it, or through core licensing. Under new agreements, SQL Server Enterprise is licensed per core. Core licensing does not require additional SQL CALs.
- 01Standard: Server/CAL or per-core licensing.
- 02Enterprise: generally licensed per core.
- 03Physical server: license every core, with at least 4 core licences per processor.
- 04Individual VM: at least 4 core licences; subscription or active Software Assurance required.
- 05SQL CALs and Windows Server CALs are separate access rights.
Explained simply · The essential terms
Three essential SQL Server terms
SQL Server is database software. Depending on the licensing model, you count either users and devices or processor cores.
SQL Server Standard
A database edition for typical business applications, available under Server/CAL or core licensing.
SQL CAL
An access licence for one user or one device under SQL Server's Server/CAL model.
Core licence
A licence for a physical or eligible virtual processor core, with at least four licences per processor or VM.
A practical example: Ten known employees use an internal database. SQL Server Standard with one server licence and ten User CALs may fit. For a public application with many unknown users, core licensing can make more sense.
Understand the job first
What exactly is SQL Server?
SQL Server is database software. It stores and processes information for accounting tools, ERP systems, patient-management applications, and websites.
The server's operating system
Windows Server provides the technical foundation on which applications can run. Its Windows licensing requirements must be assessed separately.
The database behind the application
SQL Server manages the application data. A Windows Server licence does not automatically include a SQL Server licence.
A Windows server running a SQL database requires the operating-system rights and SQL Server rights to be assessed independently.
Choose the right edition
Standard, Enterprise, Developer, or Express?
The right edition depends on the application's size, the technical features required, and whether the system is used in production.
| Edition | Suitable for | Licensing |
|---|---|---|
| SQL Server Standard | Typical business applications and mid-sized databases | Server/CAL or per core |
| SQL Server Enterprise | Large, business-critical, or heavily virtualised databases | Generally per core under new agreements |
| SQL Server Developer | Development and testing, but not production | Free Developer editions; Standard Developer and Enterprise Developer in 2025 |
| SQL Server Express | Small production databases within technical limits | Free; SQL Server 2025 allows up to 50 GB per database |
SQL Server 2025 Standard supports up to four processors or 32 cores, whichever is lower. Earlier SQL Server releases can have different limits.
The two licensing models
Server/CAL or per core: What is the difference?
Under Server/CAL, you license the database instance and its users or devices. Under the core model, processing capacity is licensed and SQL access does not require additional user CALs.
| Licensing model | What is counted? | When does it usually fit? | SQL CALs needed? |
|---|---|---|---|
| SQL Server Standard + CAL | Server licence plus accessing users or devices | A known, manageable number of users | Yes, for each accessing user or device |
| SQL Server Standard Core | Physical cores or eligible virtual cores | Many, changing, or difficult-to-count users | No additional SQL CALs |
| SQL Server Enterprise Core | Physical cores or eligible virtual cores | Advanced requirements or Enterprise features | No additional SQL CALs |
When ten known employees use an internal database application, Standard with one server licence and ten User CALs may fit. For a public application serving many customers, core licensing is often simpler because individual SQL users do not need separate CALs.
Understand SQL access
When does someone need a SQL CAL?
With SQL Server Standard under Server/CAL, each accessing user or device needs an appropriate SQL CAL, even when the database is reached indirectly through an application.
One person uses several devices
An employee accesses an application backed by SQL Server from a laptop and an office PC. A SQL User CAL may be the right access licence.
Several people share one device
Three employees share one workstation across different shifts. A SQL Device CAL may fit that shared device.
The application does not replace a SQL CAL
Twenty people use an ERP system that connects to SQL Server using one technical service account. The actual users or devices behind the application still count.
A Windows Server CAL does not automatically grant access to SQL Server. Equally, a SQL CAL does not replace a required Windows Server CAL.
Count physical cores simply
How many SQL core licences does a physical server need?
The physical core model requires every physical processor core in the server to be licensed. Microsoft requires at least four core licences per physical processor.
| Hardware | Actual cores | SQL core licences | Why? |
|---|---|---|---|
| 1 processor with 2 cores | 2 | 4 | Minimum of 4 core licences per processor |
| 1 processor with 4 cores | 4 | 4 | All 4 cores are covered |
| 2 processors with 6 cores each | 12 | 12 | Every actual physical core must be licensed |
SQL Server generally requires at least four core licences per processor. The Windows Server minimums of eight per processor and 16 per server must not automatically be applied to SQL.
License virtual SQL Servers
How is SQL Server inside a VM licensed?
When an individual virtual machine qualifies for per-VM licensing, count the vCores assigned to it. Each VM needs at least four SQL core licences.
| Virtual machine | Assigned vCores | Required SQL core licences |
|---|---|---|
| Small SQL VM | 2 vCores | 4 core licences |
| Typical SQL VM | 4 vCores | 4 core licences |
| Larger SQL VM | 8 vCores | 8 core licences |
Licensing every physical core with Standard does not automatically permit Standard instances in any number of VMs. Standard physical-core rights generally cover the physical operating system; virtual scenarios need appropriate per-VM rights or Server/CAL rights.
Enterprise and virtualisation
When does SQL Enterprise allow unlimited virtual servers?
Enterprise can make sense when many SQL instances run on the same physical host. Unlimited virtualisation does not come automatically just because the edition is called Enterprise.
| 16 physical cores licensed with Enterprise | SQL operating-system environments allowed | Important |
|---|---|---|
| Enterprise without active Software Assurance or a subscription | Up to the number of assigned core licences: 16 in this example | Additional environments require suitable additional rights |
| Enterprise with active Software Assurance or an eligible subscription | Unlimited physical or virtual SQL environments | The complete host must be fully licensed with Enterprise |
Windows Server and SQL Server have separate licensing rules. Even when the operating system permits Datacenter virtualisation, SQL Server still requires its own appropriate licences.
High availability made simple
Does a passive standby server also need a licence?
A passive SQL server waits to take over if the production server fails. Whether additional SQL licences are needed depends particularly on Software Assurance or an eligible subscription.
Passive instances are not automatically covered
A regular SQL licence does not automatically include special failover rights. A second server or VM must therefore be assessed separately.
Additional passive failover rights may be included
For each primary workload, Microsoft describes one passive high-availability instance, one passive disaster-recovery instance, and one additional passive disaster-recovery instance in Azure, subject to the applicable terms.
The standby instance must not serve production SQL data to users or devices or run an active production SQL workload. Reporting and other active uses must be licensed separately.
A practical decision guide
Which SQL licensing model fits which situation?
| Situation | Likely model | Also check |
|---|---|---|
| Internal application with a small known user group | Consider SQL Server Standard + CAL | User CALs or Device CALs and indirect access |
| Many customers or unknown access volumes | Consider SQL Server Standard Core | Physical or virtual cores and VM eligibility |
| Many virtual SQL instances on one host | Consider SQL Server Enterprise Core | Full host licensing plus active SA or a subscription |
| Development or testing without production use | Consider SQL Server Developer | No production use |
| Small production database | Consider SQL Server Express | Technical limits and database size |
A practical checklist
Questions to answer before buying
- 01Do you actually need SQL Server Standard or Enterprise?
- 02Do you know the number of users or devices accessing it?
- 03Should you choose Server/CAL or core licensing?
- 04Will SQL Server run directly on physical hardware or inside a VM?
- 05Have you included at least four core licences per processor or eligible VM?
- 06Do you have active Software Assurance or an eligible subscription?
- 07Are indirect access, failover servers, or Azure deployments involved?
The key takeaway
A few known users? Check Server/CAL. Many users? Check cores. Many SQL VMs? Check Enterprise and SA.
The appropriate SQL licence depends on the edition, actual access patterns, physical or virtual deployment, and additional rights. Windows Server and SQL Server always require separate assessment.
Sources and currency
Checked against official Microsoft information
The applicable Microsoft Product Terms for the agreement, purchase date, and actual deployment remain authoritative.
- 01Microsoft: SQL Server 2025 Licensing Guidance↗ – opens in a new tab
- 02Microsoft Product Terms: SQL Server↗ – opens in a new tab
- 03Microsoft Licensing: SQL Server licensing models↗ – opens in a new tab
- 04Microsoft Learn: SQL Server 2025 editions and features↗ – opens in a new tab
- 05Microsoft Learn: Pricing guidance for SQL Server on Azure VMs↗ – opens in a new tab
Editorial note: This article explains basic SQL Server 2025 licensing rules. Individual agreement terms, earlier product versions, hosting arrangements, and exceptions must be reviewed separately.