SQL Server is one of the (if not the) most complicated products from Microsoft to license. It is typically licensed per core, with different editions available to meet different needs and budgets, but that is just the tip of the iceberg.
To license SQL Server, you must purchase a license for each core on the server where you will install the software (although you may license physical cores or virtual cores if the SQL server is virtualized). The number of cores you need to license is based on the number of cores in the processor or the virtual cores, not the number of physical processors or sockets. Microsoft also has a 4 Core minimum, so even if the server or virtual SQL Instance is only 2 cores, you would have to license with 4 Cores.
There are several editions of SQL Server available, including:
- Enterprise Edition: This is the most feature-rich and powerful edition of SQL Server. It is designed for mission-critical applications and large-scale data warehousing.
- Standard Edition: This edition is suitable for small to medium-sized businesses and includes many of the same features as Enterprise Edition but with some limitations on scalability and performance.
- Express Edition: This free edition of SQL Server is suitable for small applications and is limited to a single processor and 10 GB of database storage. Express is a free edition of SQL Server.
- Developer Edition: This edition is a full-featured version of SQL Server licensed for development and testing. It cannot be used for production environments.
To purchase a license for SQL Server, you can contact a Microsoft reseller or visit the Microsoft website.
How Do You Count Cores For SQL Server Licensing On A Physical Server?
To count the cores for SQL Server licensing, you need to determine the number of cores in the processors where you will be installing the software. Here are the steps to follow:
- Identify the servers where you will be installing SQL Server.
- Determine the number of processors in each server.
- Count the number of cores in each processor.
- Multiply the number of cores in each processor by the number of processors in the server, accounting for the fact that there is a 4 Core Minimum.
- Add the total number of cores for all servers where you will be installing SQL Server.
For example, if you have a server with 2 processors, each with 6 cores, the total number of cores for that server would be 12. If you have a second server with a single processor with 4 cores, the total number of cores for that server would be 4. The total number of cores for both servers would be 16.
You will need to purchase a license for each of these cores. SQL Server is typically licensed per core, with different editions available to meet different needs and budgets.
What Is The Minimum Number Of Cores You Need To License For A Physical Install of SQL Server?
The minimum number of cores you need to license for SQL Server depends on the edition of the software that you are using.
For the Standard and Enterprise editions, the minimum number of cores you need to license is 4 per physical processor. If you have a server with a single processor with 4 or more cores, you will need to purchase a license for at least 4. If you have a server with two processors, each with 4 or more cores, you will need to purchase a license for at least 8 cores (4 cores per processor).
For the Express edition, there is no minimum number of cores you need to license, as this edition is free and limited to a single processor and 10 GB of database storage.
It’s important to note that you need to license all the cores in the processors of the servers where you will be installing SQL Server, regardless of whether you will use all the cores.
How Do You License SQL in a Virtualized Environment?
In a virtualized environment, you must license SQL Server for each virtual machine (VM) running the software. You can use either the Physical Core-Based Licensing model or the Virtual Core-Based Licensing model to license SQL Servers in a virtualized environment.
Under the Physical Core-Based Licensing model, you must purchase a license for each physical core on the host server, regardless of the number of VMs or cores allocated to the VMs.
Under the Virtual Core-Based Licensing model, you must purchase a license for each virtual core (vCore) allocated to the VM. The number of vCores you need to license is based on the number of cores allocated to the VM, not the number of physical cores on the host server.
For both the Physical and Virtual models, you still need to purchase a minimum of 4 Cores.
To determine the number of vCores that you need to license for a VM, you can use the following formula:
Number of vCores = (Number of physical cores on the host server / Number of VMs on the host server) * Number of cores allocated to the VM
For example, if you have a host server with two processors, each with 6 cores, and you have two VMs running on the host server, with each VM allocated 2 cores, the number of vCores that you would need to license for each VM would be 4 (not 3 as you have a 4 core minimum to account for).
How Do I Optimize My SQL Server Licensing For Cost Savings
There are a few ways that you can optimize your SQL Server licensing for cost savings:
- Consider using the Virtual Core-Based Licensing model: If you are running SQL Server in a virtualized environment, you may save money using the Virtual Core-Based Licensing model instead of the Physical Core-Based Licensing model. Under this licensing model, you only need to purchase a license for the number of virtual cores (vCores) allocated to each virtual machine (VM) rather than a license for each physical core on the host server. Don’t forget about the 4 core minimum rule when calculating this.
- Use the appropriate edition of SQL Server: Choose the edition of SQL Server that best meets your needs and budget. The Enterprise edition is the most feature-rich and powerful, and expensive. The Standard edition is suitable for many small to medium-sized businesses. It includes many of the same features as the Enterprise edition but with some limitations on scalability and performance. The Express edition is free for small applications and limited to a single processor and 10 GB of database storage.
- Optimize your hardware: Consider using processors with fewer cores or allocating fewer cores to each VM. This can help you reduce the number of cores that you need to license and save money on your SQL Server licenses.
- Use software assurance: Consider purchasing software assurance for your SQL Server licenses. Software Assurance (SA) is needed when there is server mobility occurring in a virtual environment (or to be allowed to use on 3rd party clouds – check the rules before deploying to any 3rd party cloud). The SA allows a virtual SQL Server to move between hosts and have the licenses follow it. This is a very complicated license scenario, and you need to ensure you understand the rules when calculating requirements. SA also gives you access to new software versions as they are released.
- Use the cloud provider’s licensing: If you are running SQL Server in a public cloud environment, such as Microsoft Azure or Amazon Web Services (AWS), you may save money by using the cloud provider’s licensing instead of purchasing your own licenses. Azure and AWS offer pay-as-you-go pricing for SQL Server, allowing you to only pay for the resources you use. This can be a cost-effective option, especially if you have variable or unpredictable workloads.
How a software asset management (SAM) tool such as MetrixData 360’s SQL Server License Optimization Tool can help you optimize your SQL Server licensing:
- License optimization: A SAM tool can help you optimize your SQL Server licensing by identifying underutilized licenses and recommending consolidation or redistribution. This can help you save money on your SQL Server licenses by ensuring you are not paying for more than you need.
- Compliance reporting: A SAM tool can help track your SQL Server usage and ensure that you comply with your licensing agreements. It can provide you with reports that show how you are using your licenses and help you identify any potential compliance issues.
- Software usage tracking: A SAM tool can help you track your SQL Server usage and identify opportunities for cost savings. It can provide reports on your usage patterns and help you understand how you use your licenses. This can help you identify underutilized licenses and make informed decisions about your licensing strategy.
