It is designed for heavy usage internet deployments. This model is used when number of users or clients connecting to the server are not exactly known. It is bought in a pair for two cores and needs to be bought at least for four cores. – an internal workload as opposed to a web facing database).CORE Licensing:ĬORE Licensing requires us to buy license for all the core present on a physical server. This is great in instances where the number of users will remain relatively consistent (i.e. CAL Licensing is best when the number of clients accessing the Database Server are known (and small in number). One license is bought for entire database server and then user or device CALs are bought separately. A CAL is needed for each client that accesses the server. These are:Client Access Licensing (CAL) ModelCore Licensing ModelCAL Licensing:ĬAL licensing is for clients that connect to the server. The selection between them is made on the based on the number of clients. It basically comes down to the number of clients.
MICROSOFT SQL USER CAL HOW TO
This guide will help you determine how to best license your environment. The CAL model is based off of the number of users accessing the database. The core model is based off the number of cores the physical server has.
There are two types of licensing scenarios with SQL 2017 – the CORE model and the CAL model. I think you could do CALs for the second server. This is what I read the other day that helped us decide.