Activating SQL Server 2017 Standard 50 Device CAL
Activating SQL Server 2017 Standard 50 Device CAL involves the correct deployment of the server licence and ensuring compliance with access for devices that connect to the SQL Server service. In practice, this means that one server licence covers the installation of the SQL Server 2017 Standard environment itself, and the Device CAL model allows legal use of it from a specified number of devices, regardless of the number of users operating the workstation.
The 50 Device CAL variant is most often chosen where multiple people use one computer, terminal, or device, such as in a warehouse, reception, production, sales points, or in a shift environment. This model can be more beneficial than User CAL if the number of devices is easy to count and does not change frequently.
It is worth remembering that in the case of SQL Server 2017 CAL, each CAL licence is not usually activated with a separate key in the system. The product key typically concerns the server installation itself, while CAL rights must be possessed, documented, and assigned in accordance with licensing rules. Therefore, correct activation involves not only entering the key but also ensuring that the deployment corresponds to the purchased licensing model.
Step by Step
-
Ensure you have the correct licensing product.
For the SQL Server 2017 Standard 50 Device CAL scenario, you need:- a SQL Server 2017 Standard Server licence,
- a package or the appropriate number of Device CAL licences,
- a purchase document or licensing confirmation.
-
Prepare the server for installation or verification of an existing installation.
Check if the environment is running on SQL Server 2017 Standard, and not on the Express, Enterprise, or Evaluation edition. This is important because the CAL model refers to the appropriate server edition. -
Install or run the SQL Server 2017 configurator.
If the installation is new, during deployment, select the correct product edition and enter the key if the installer requires it. In some cases, installation can also occur on media or an image assigned to a specific licensing channel. -
Complete the instance and service configuration.
Set the instance name, service accounts, data locations, and authentication mode according to the environment's needs. The technical configuration itself does not replace the CAL licence, but it must be consistent with the intended use of the server. -
Verify the server access model.
In the Device CAL model, devices that connect to SQL Server directly or indirectly are licensed. If 50 specific devices use the server, the environment should be covered by 50 Device CAL. If there are more devices, the licensing needs to be extended. -
Maintain licensing documentation.
For audit compliance, store:- purchase confirmation,
- product data,
- the number of CALs purchased,
- licence assignment to the environment,
- information about the server and devices using the system.
-
Label and describe the deployment internally.
Good practice is to prepare a brief administrative note: which server supports SQL Server 2017, how many devices have access, and on what licensing basis the environment operates. This facilitates later checks and infrastructure expansion.
For any further assistance or questions, please contact us at [email protected] or call 00 800 121 1654.
Checking
After activation and deployment, it is worth checking two areas: technical and licensing.
From a technical point of view, make sure that:
- the SQL Server service is working properly,
- the instance starts without errors,
- client applications connect to the database,
- a trial version or incorrect edition has not been installed.
From a licensing point of view, check if:
- the SQL Server 2017 Standard edition is being used,
- you have a valid proof of purchase,
- the number of devices with access does not exceed 50,
- the Device CAL model corresponds to the actual way of using the system.
If the environment is developing dynamically, it is a good idea to periodically recalculate the devices with access to the server. This is a simple way to avoid licensing inconsistencies.
Problems
The most common problem is confusing product key activation with CAL license activation. In the case of SQL Server 2017 CAL, simply entering the key into the installer does not yet mean full licensing compliance. CALs are access rights and must correspond to the actual number of devices.
Another common mistake is using the wrong model. If multiple people work from one device, Device CAL usually makes sense. However, if many users use different computers, laptops, and mobile devices, the User CAL model may be better.
Lack of documentation is also a problem. Even a properly deployed SQL Server can cause difficulties during verification if the company does not have proof of purchase or does not know how many devices actually use the system.
Doubts also arise when it comes to indirect access, for example, through a company application, terminal, or ERP system. Such access must also be taken into account in licensing if the end devices use SQL Server data or functions.
If you are unsure whether your configuration is compliant with licensing rules, please contact us: [email protected] or call 00 800 121 1654.
FAQ
Does 50 Device CAL mean 50 users?
No. In the Device CAL model, devices are licensed, not people. Multiple users can use one licensed device.
Are CAL licenses activated with a separate key?
Mostly not in the same way as the server product itself. The key usually concerns the installation of SQL Server, while CALs are licensing rights that must be possessed and properly assigned to the environment.
How do you know whether Device CAL or User CAL is better?
It depends on the way of working. If many people use the same workstations or terminals, Device CAL is usually more beneficial. If one user works on multiple devices, User CAL is often more cost-effective.
In case of questions regarding activation, licensing compliance, or selecting the right model for SQL Server 2017 Standard 50 Device CAL, write to [email protected].