Microsoft SQL Server licensing in container deployments
Summarize
Summary of Microsoft SQL Server licensing in container deployments
The Software Asset Management (SAM) publisher pack for Microsoft supports licensing rules for Microsoft SQL Server products deployed via Docker containers in both on-premise and cloud environments. Containers package application code and dependencies to ensure consistent deployment across different computing environments without reconfiguration. Each container virtualizes an operating system, enabling multiple isolated applications on the same physical server.
Show less
SAM works with ServiceNow® Discovery to identify containers running Microsoft SQL Server, the Kubernetes clusters supporting them, the underlying physical server OS, the SQL Server version and edition deployed, and the number of virtual processor cores assigned to each container. This data enables the creation of software installation records for containers, allowing effective license compliance tracking and optimization for SQL Server products deployed in containerized environments.
Supported licensing models
The Microsoft publisher pack supports two main licensing models for SQL Server in containers:
- Per core licensing: Each container is licensed as a standalone device. Licensing is based on the number of virtual CPUs (vCPUs) assigned to the container, with a minimum of four core licenses per container.
- Server/CAL licensing: Each container requires a server license (either per instance or per server). Additionally, each user or device accessing the physical server hosting the containers must have a corresponding Client Access License (CAL). Server licenses cover container-based installations on physical servers, with per instance licenses for specific installations and per server licenses for all installations on a server. User CALs license individual users regardless of device count, and device CALs license devices regardless of user count.
Key outcomes
- Accurate discovery and inventory of Microsoft SQL Server deployments in containerized environments, including Docker and Kubernetes details.
- Creation of container-based software installation records for precise license reconciliation and compliance management.
- Support for both per core and server/CAL licensing models tailored to container deployments.
- Access to the Licensable Software Products Deployed on Containers report for enhanced visibility into containerized SQL Server software across on-premise and cloud settings.
The Software Asset Management publisher pack for Microsoft supports licensing rules for Microsoft SQL Server products that are deployed across both on-premise and cloud environments using Docker containers.
Containers are executable software packages that bundle all the code and dependencies that are required for deploying and running a specific application. With a container, you can deploy and run the same application uniformly across any computing environment, such as a desktop computer or the cloud, without having to reconfigure the application. Each container also virtualizes an operating system (OS) so that you can quickly and easily deploy multiple isolated applications within the same computing environment.
- The Docker containers through which your Microsoft SQL Server products are deployed.
- The corresponding Kubernetes clusters that enable each container to run.
- The OS of the underlying physical server that the container is running on.
- The Microsoft SQL Server version and edition that is deployed through each container.
- The number of virtual processor cores that are assigned to each container.
The Software Asset Management application uses the resulting data to create corresponding software installation records for each of your discovered containers. You can then reconcile these container-based software installations to track and optimize the license compliance of the Microsoft SQL Server products that are deployed through each container.
For more visibility into the Microsoft SQL Server products that are deployed through your Docker containers, view the Licensable Software Products Deployed on Containers report.
For more information on Docker discovery, see Docker virtualization. For more information on Kubernetes discovery, see Kubernetes discovery.
Supported licensing models
| Licensing Model | Description |
|---|---|
| Per core | You must license each container as a standalone device. Licensing is based on the number of virtual CPUs (vCPUs) that are discovered on each container, with a minimum of four per core licenses per container. |
| Server/CAL | You must license each container using a server (per instance or per server) license. You must also license each user or device that is accessing the underlying physical server running these containers using a user or device CAL license. Server licenses enable you to license container-based software installations on your physical servers. To license only a certain number of installations on a physical server, use a server (per instance) license. To license all installations on a physical server, use a server (per server) license. CAL licenses are client access licenses that grant a set number of users or devices
access to the underlying physical server on which your containers are running.
|