Activating SQL Server 2016 Standard 50 User CAL

Licensing SQL Server 2016 Standard 50 User CAL refers to a model where the server has a SQL Server Standard Server license, and additional User CAL licenses are assigned to specific users. In practice, this variant works well in companies where a fixed number of employees use the system, also from different devices. The 50 User CAL package allows you to legally provide server resources to a maximum of fifty named users.

It's worth remembering that in the case of SQL Server 2016 CAL, each access license is not activated separately in the operating system or in the SQL Server itself, as is the case with some other Microsoft products. The key is to properly deploy the server license, maintain licensing documents, and correctly assign CAL to users in the organization. The activation itself usually concerns the product key for the server layer, while CALs represent access rights.

Step by Step

1. Make sure you have the correct set of licenses.
   You should have:

• a SQL Server 2016 Standard Server license,
• a 50 User CAL package,
• a purchase document or license confirmation,
• a product key, if provided for editions that require key entry during installation.

1. Check which version of SQL Server is installed.
   On the server, run SQL Server Management Studio or connect to the instance and check the version. The product must match the purchased edition, i.e., SQL Server 2016 Standard. If a different edition is installed, you need to sort out the environment before proceeding.

2. Enter or verify the product key for the server.
   During the installation of SQL Server 2016 Standard, the system may ask for the product key. If the installation was done earlier and the edition is already correct, additional CAL activation is usually not required at the technical level. In the Server + CAL model, the most important thing is that the server is properly licensed, and the number of users has coverage in the purchased CALs.

3. Assign User CAL licenses to specific users.
   A User CAL license is assigned to a person, not a computer. This means that one user can connect to the server from multiple devices, but each additional user requires their own CAL license. Internally in the company, it's a good idea to prepare a list of 50 users who have been assigned permissions.

4. Maintain licensing documentation.
   Prepare and store:

• an invoice or proof of purchase,
• a license number or confirmation from the distribution channel,
• internal records of User CAL assignment,
• information about the server being licensed.

1. Verify access compliance.
   Check if more than 50 users covered by the User CAL model are using the server. If the number of users increases, it will be necessary to purchase additional access licenses.

For any questions or concerns, please contact us at [email protected] or call 00 800 121 1654.

Verification

After implementation, it is worth confirming three things. Firstly, the instance is running as SQL Server 2016 Standard. Secondly, the organisation has a server licence corresponding to this installation. Thirdly, there is an internal list of users covered by the 50 User CAL package.

Additionally, it is a good idea to check who actually uses the applications and databases connected to the server. If, in practice, access is also available to people outside the list, the environment may require licence extension. The SQL Server itself does not always show this directly as "activated CAL", because CAL is a licence right, not a separate component activated in the product console.

Problems

The most common problem is assuming that SQL Server 2016 CAL needs to be "entered" or activated in the same way as the product key. In most implementations, this does not work. Technically, the server or the installed edition is activated, while CALs are confirmation of the right of access for users.

Another common mistake is confusing User CAL with Device CAL. If 50 User CAL has been purchased, the licences apply to users, not computer stations. You should not keep records solely by device.

Lack of documentation can also be a problem. Even if the environment works correctly, the lack of purchase confirmation and the lack of assignment of CAL to users can cause organisational and licensing difficulties. Therefore, it is worth keeping a simple register with the name, surname, department, and date of licence assignment.

If, after installation, it turns out that a different version than Standard is running, or the system was installed from an evaluation medium, a change of edition or reconfiguration of the installation may be necessary. In such a situation, it is best to first determine the exact state of the environment and only then take action.

FAQ

Is SQL Server 2016 Standard 50 User CAL activated with a separate key?
Usually not. A separate key usually applies to the server installation itself, and User CAL is the right of access assigned to users. The most important thing is to properly licence the server and keep records of assigned CALs.

Can one user use multiple computers?
Yes. In the User CAL model, the licence is assigned to the person. Such a user can connect to the SQL Server from an office computer, laptop, or other device, as long as they remain the same user.

What to do when more than 50 people use the system?
Then the 50 User CAL package is no longer sufficient. You need to purchase additional access licences or analyse whether a different licensing model would be more cost-effective.

If you need help with selecting, verifying, or organising SQL Server 2016 CAL licences, write to: [email protected].