What is included in Windows Server 2025 Standard (16 Core) & 5 User CALs & SQL Server 2025 Standard?

Server OS – Windows Server 2025 Standard operating system.
16 cores – Core-based Windows Server Standard package.
Five users – Windows Server access for five assigned users.
SQL Standard – SQL Server 2025 Standard database engine.
Eight cores – SQL Server Standard eight-core purchase option.
Important – RDS rights and Enterprise-only SQL features are excluded.

Windows Server 2025 Standard 16-core (1 User) in detail
See the Windows Server edition and included server capabilities

Windows Server 2025 User CAL (5) in detail
See the Windows Server CAL package and access model

Why buy Windows Server 2025 Standard, 5 User CALs and SQL Server 2025 Standard together?

This combination is intended for a Windows Server 2025 Standard application or database server where five assigned users need Windows Server access and SQL Server 2025 Standard runs the production databases. Microsoft explicitly supports SQL Server 2025 Standard on Windows Server 2025 Standard, while the Windows Server User CALs cover Windows Server access and the core-based SQL Server package does not require separate SQL CALs.

Supported platform – SQL Server 2025 Standard supports Server 2025 Standard.
Server access – Five CALs cover five assigned Windows users.
SQL access – Core-based SQL requires no separate SQL CALs.
Database services – SQL Server runs directly on supported Server 2025.
User mobility – Assigned users may access Windows from different devices.
SQL Agent – Standard supports scheduled SQL Server Agent jobs.

Do Windows Server 2025 Standard and SQL Server 2025 Standard work together?

Yes. Microsoft lists Windows Server 2025 Standard as a supported operating system for SQL Server 2025 Standard. SQL Server 2025 also supports Windows Server 2025 Datacenter, Datacenter: Azure Edition and Essentials, as well as supported Windows Server 2022 and 2019 editions. For this bundle, Windows Server 2025 Standard provides the operating system on which the SQL Server 2025 Standard database engine can run. The five Windows Server User CALs separately provide the required Windows Server access rights for five assigned users.

In which order should Windows Server, the User CALs and SQL Server be set up?

Install and configure Windows Server 2025 Standard first, then install SQL Server 2025 Standard on that supported Windows Server environment. The Windows Server User CALs are access rights assigned to users, not software applications that must be installed before SQL Server. SQL Server Setup therefore depends on the operating system being in place, while the CAL assignment is an access-rights matter rather than a SQL installation prerequisite. If Windows Server is intended to operate as an Active Directory domain controller, Microsoft specifically recommends against installing SQL Server on that domain controller for security reasons.

Who is this three-product bundle for?

This bundle fits a server that will run Windows Server 2025 Standard and SQL Server 2025 Standard for a business application used by five assigned people. A typical example is an ERP, inventory, CRM or line-of-business application whose program services and SQL databases run on the same Windows Server while the employees connect from their workstations or notebooks. User CALs fit this scenario when the same employees may use more than one device. The combination is less appropriate when SQL Server will run on a separate database server, when the machine is primarily a domain controller, or when the access pattern favors Device CALs.

Do the five Windows Server User CALs also cover SQL Server access?

The Windows Server User CALs cover Windows Server access; they are not SQL Server CALs. However, the SQL Server component in this bundle is identified as an eight-core SQL Server Standard product, and Microsoft states that SQL Server Standard licensed under the core model does not require separate client access CALs for users or devices accessing SQL Server. The two access models therefore perform different jobs: Windows Server CALs cover Windows Server access, while the SQL Server core entitlement covers the database engine without a per-user SQL CAL requirement. Buyers should still verify that the SQL core quantity purchased matches the SQL environment being deployed.

When should you buy these products separately instead?

Buy the products separately when all three are not required for the same deployment. If Windows Server 2025 Standard is already available, only the required access rights and SQL component may be needed; if suitable Windows Server CALs already exist, there is no reason to duplicate them. SQL Server should also be selected separately if its required core quantity differs from the eight-core package in this bundle. If SQL Server will be placed on another server or virtual environment, plan that SQL deployment independently rather than assuming this three-product configuration matches it.

What does this bundle not cover?

This bundle does not include Remote Desktop Services access rights. Microsoft requires additional RDS CALs when users or devices access functionality covered by Remote Desktop Services. SQL Server Standard also does not contain every capability of SQL Server Enterprise; for example, Microsoft's SQL Server 2025 edition matrix lists star-join query optimizations and parallel query processing on partitioned tables and indexes as Enterprise-only. The bundle should therefore not be treated as an RDS package or as an Enterprise SQL deployment.

Frequently asked questions about Windows Server 2025 Standard (16 Core) & 5 User CALs & SQL Server 2025 Standard

Can SQL Server 2025 Standard be installed directly on Windows Server 2025 Standard?

Yes. Microsoft's SQL Server 2025 operating-system matrix explicitly lists Windows Server 2025 Standard as supported for SQL Server 2025 Standard. Windows Server 2025 Core is also among the supported Server Core platforms for SQL Server 2025.

Does SQL Server 2025 Standard include SQL Server Agent?

Yes. Microsoft's SQL Server 2025 edition comparison lists SQL Server Agent as available in Standard and Enterprise but not Express. This matters for database environments that use scheduled SQL jobs, maintenance tasks or other Agent-based automation.

Should SQL Server be installed on a Windows Server domain controller?

Microsoft recommends against it. SQL Server Setup documentation specifically says not to install SQL Server on a domain controller for security reasons and documents additional limitations for that configuration. If this Windows Server will primarily serve as the domain controller, plan the SQL workload on a separate server or suitable virtual environment instead.