Did you know there is a number of different ways to license SQL Server?

Per Core – this is now the most common way to license SQL Server. Per Core licensing for SQL means you don’t need to purchase SQL CALs for your internal users and also includes rights for your external users to access SQL. Both Standard and Enterprise versions of SQL come in the per core model.

You can license either by physical cores or by VM.

When you are licensing physically then the following applies:

  • Each server running SQL Server software or any of its components (such as Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server core licenses
  • When licensing the physical server, all physical cores must be licensed with a minimum of 4 cores per physical processor
  • Note: The use of hyper-threading technology does not affect the number of core licenses required when running SQL Server software in a physical OSE

When you license via OSE (operating system environment) or VM:

  • All virtual cores (v-cores) supporting virtual OSEs that are running instances of SQL Server software must be licensed
  • 4 core minimum per VM
  • Additional licenses are required when:
    • A single hardware thread is supporting multiple virtual cores. (A core subscription license or license with Software Assurance is required for each v-core.)
    • Multiple hardware threads are supporting a single virtual core simultaneously. (A core license allows a single v-core to be supported by a single hardware thread.)
  • Licensing per VM means the license can move around your server farm with your VM.

 

Per Server with CALs – Although enterprise used to come in per server versions you can not buy this any more so this is just for Standard edition.

 

  • To license VMs using the Server+CAL model, simply purchase one server license for each VM running SQL Server software, regardless of the number of virtual processors allocated to the VM
  • Each operating system environment (OSE) running SQL Server software or any of its components must have a SQL Server server license assigned to the physical server hosting the OSE. Each server license allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual
  • Running SQL Server software on different hardware partitions or blades requires separate software licenses. Hardware partitions and blades are considered to be separate servers for licensing purposes and SQL Server software licenses cannot be assigned to more than one server at any time
  • Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly
  • For human operated devices such as PCs or hand-held terminals, a user CAL or device CAL can be used
  • CALs must be for the version of SQL Server being accessed or a later version.
  • Note: The use of hardware or software that reduces the number of devices or users that directly access or use the software (multiplexing/pooling) does not reduce the number of CALs required

 

So to put it simply, if your end user requires SQL Standard Edition, and has a smallish number of only internal users/devices accessing the server, it’s worth pricing up per server and CAL as an option.