In short
SQL Server 2025 licensing has two main commercial models:
- Per Core — available for SQL Server 2025 Standard and Enterprise. You license the compute running SQL Server; users and devices do not need SQL Server CALs under this model.
- Server + CAL — available for SQL Server 2025 Standard only. You license the server software and also license every user or device that accesses SQL Server, including many indirect-access scenarios.
For hosted or virtual SQL Server, the harder question is often not Standard vs Enterprise. It is who supplies the SQL Server license and which Microsoft rights allow it to run on the chosen infrastructure.
For most self-managed hosted SQL Server workloads with many or unpredictable users, Per Core is the simpler model to evaluate because it does not require counting every accessing user or device. Server + CAL can be attractive for a controlled Standard-edition environment with a small, countable population.
This guide owns the SQL Server licensing-model decision. For edition features, use MSSQL Standard vs Enterprise — When to Pay More. For installation, use Install SQL Server 2025 on a Windows Server VPS. For Windows Server OS licensing, use Windows Server Licensing on Raff.
Licensing note: Microsoft licensing rights depend on the agreement, purchase channel, Software Assurance or subscription status, deployment model, and provider. Microsoft Product Terms and the customer’s executed agreement control if they differ from this guide.
SQL Server 2025 licensing models at a glance
Microsoft’s current SQL Server licensing guidance identifies these commercial options:
| SQL Server 2025 edition | Per Core | Server + CAL |
|---|---|---|
| Standard | Yes | Yes |
| Enterprise | Yes | No |
That means the licensing decision is not identical for every edition.
If you already know you need Enterprise, the commercial licensing model is Per Core. If Standard fits the workload, you can evaluate either Per Core or Server + CAL.
Per Core licensing: pay for compute, not SQL CALs
Under the Per Core model, SQL Server licenses are assigned according to the physical cores or virtual cores that run SQL Server, depending on the licensing approach being used.
The main advantage is operational simplicity:
Licensed SQL compute → users and devices can access SQL Server → no separate SQL Server CAL for each user/device
This can be a better fit when:
- the application has many users;
- users are external or difficult to count;
- applications, services, devices, APIs, or middleware access SQL Server;
- the user/device population changes frequently;
- the database is part of a hosted business application;
- CAL administration would be more complex than core licensing.
SQL Server core licenses are sold in two-core packs, but licensing calculations are based on the number of required core licenses, not simply the number of packs purchased.
Licensing SQL Server 2025 by virtual machine
Microsoft currently allows SQL Server 2025 Standard and Enterprise to be licensed by virtual machine under the Per Core model when the licenses have active Software Assurance or are qualifying subscription licenses.
For a licensed virtual operating system environment (virtual OSE), Microsoft requires licenses for the virtual cores allocated to that VM, subject to a minimum of four core licenses per virtual OSE.
If a virtual core maps to more than one hardware thread, Microsoft also requires licensing the hardware threads to which that virtual core is mapped.
The practical consequence for a small Windows VM is important:
A very small VM does not automatically create a two-core SQL Server licensing requirement. Under Microsoft’s eligible per-VM core model, the minimum is four core licenses per VM.
Example core-count planning
Assume each vCPU exposed to the VM represents one virtual core and no virtual core maps to multiple hardware threads. Under that simplified assumption:
| Windows VM | Virtual cores to consider | Minimum SQL core licenses under eligible per-VM model |
|---|---|---|
| 2 vCPU | 2 | 4 |
| 4 vCPU | 4 | 4 |
| 6 vCPU | 6 | 6 |
| 8 vCPU | 8 | 8 |
| 16 vCPU | 16 | 16 |
This table is a planning example, not a substitute for checking the actual virtualization mapping and Microsoft entitlement.
The four-core minimum matters commercially because infrastructure sizing and SQL licensing cost do not scale identically at the smallest VM sizes.
Physical-server Per Core licensing is different
When licensing a physical server by cores, Microsoft requires enough SQL Server core licenses for the physical cores, with a minimum of four core licenses per physical processor.
Do not copy a physical-host calculation into a virtual-machine calculation. Microsoft treats these as different licensing approaches with different use rights.
This distinction becomes especially important in highly virtualized environments where Enterprise edition plus qualifying Software Assurance or subscription rights can provide broader virtualization benefits.
Server + CAL licensing is Standard-only
SQL Server 2025 Standard can also be licensed using the Server + CAL model.
At a high level:
SQL Server Standard server license + SQL Server CAL for every accessing user or device
A single SQL Server CAL assigned to a user or device can allow that licensed user or device to access more than one properly licensed SQL Server, subject to Microsoft’s terms.
Server + CAL is worth evaluating when:
- the environment uses Standard edition;
- the population is small;
- users or devices are easy to count;
- access is internal and predictable;
- the organization already manages Microsoft CALs cleanly;
- future growth is unlikely to make CAL administration expensive.
It becomes less attractive when the database is accessed by a large, changing, public, customer-facing, or difficult-to-count population.
Multiplexing does not reduce SQL CAL requirements
This is one of the most common SQL Server licensing mistakes.
Putting an application server, API, connection pool, middleware layer, or other multiplexing technology between users and SQL Server does not automatically reduce the number of SQL Server CALs required under Server + CAL licensing.
Conceptually:
100 users ↓ Web / ERP / application server ↓ One SQL connection pool ↓ SQL Server
The fact that SQL Server sees a smaller number of technical connections does not mean only those connection-pool identities need CALs.
Microsoft explicitly states that hardware or software used to reduce the number of users or devices directly accessing SQL Server does not reduce the required CAL count.
For a customer-facing or high-user application, this is one reason Per Core licensing is often easier to model.
Per Core vs Server + CAL: decision table
| Situation | Usually evaluate first | Why |
|---|---|---|
| Small internal app with 5 known users | Server + CAL or Per Core | Both may be viable; compare total licensing and admin overhead |
| 50 employees using an ERP | Per Core | CAL count can become material |
| Public web application backed by SQL Server | Per Core | End users are difficult or impractical to license individually |
| Devices/services access SQL indirectly | Per Core often simpler | Multiplexing does not erase CAL requirements |
| Enterprise edition required | Per Core | Server + CAL is not available for Enterprise |
| User count changes frequently | Per Core | Avoid recurring CAL-count administration |
| Small stable Standard-edition environment | Server + CAL can be viable | Predictable user/device population may favor CAL economics |
Do not choose the model from a generic internet calculator alone. Model the real users, devices, VM cores, edition, growth plan, and deployment rights.
SQL Server edition choice and licensing choice are separate decisions
Do not collapse these into one question.
First ask:
What SQL Server features and scale does the workload need?
Then ask:
How should that edition be licensed in this deployment?
For SQL Server 2025, Standard supports many SMB and mid-market production workloads and Microsoft currently documents a 32-core maximum compute capacity for Standard. Enterprise is intended for workloads requiring higher scale and additional enterprise capabilities.
The canonical feature decision is covered in MSSQL Standard vs Enterprise — When to Pay More.
This page stays focused on licensing.
Developer, Evaluation, and Express are not normal paid-production substitutes
SQL Server 2025 also includes specialty/free editions.
Microsoft identifies Standard Developer, Enterprise Developer, and Evaluation as non-production editions. Express can be used in production within its technical and license limits.
A practical boundary is:
| Edition | Typical role |
|---|---|
| Standard Developer | Development/test against Standard feature set |
| Enterprise Developer | Development/test against Enterprise feature set |
| Evaluation | Time-limited evaluation/testing |
| Express | Small workloads that fit Express limits |
| Standard | Main paid production choice for many SMB workloads |
| Enterprise | Paid production for advanced scale/features |
Do not deploy Developer edition into production simply because the Windows VM itself is properly licensed.
Windows Server and SQL Server are separate Microsoft products with separate licensing requirements.
