<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Microsoft SQL 2022 Device CAL?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Device access right</strong> – Legal access for one shared device.<br /><strong>Server+CAL model</strong> – Pairs with a SQL Standard server license.<br /><strong>Unlimited users</strong> – Any number of people per licensed device.<br /><strong>Multi-server reach</strong> – One CAL accesses several licensed SQL servers.<br /><strong>Indirect access covered</strong> – Multiplexed app and middleware connections included.<br /><strong>Core Capacity</strong> – An access right only, no SQL software installed.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Microsoft SQL 2022 Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A SQL Server 2022 Device CAL is a Client Access License that legally permits one device to connect to a SQL Server Standard instance under the Server+CAL model. It licenses the device itself, so any user working from that machine is covered.<br /><br /><strong>Shared-device value</strong> – Cheaper than User CALs for shift work.<br /><strong>Predictable cost</strong> – Count devices instead of fluctuating staff.<br /><strong>Kiosk friendly</strong> – Fits POS, scanners, and time-clock terminals.<br /><strong>Server flexibility</strong> – Same CAL reaches multiple licensed servers.<br /><strong>Compliance proof</strong> – Satisfies audits for low user-count databases.<br /><strong>Standard pairing</strong> – Completes the Standard Server+CAL licensing setup.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does the Microsoft SQL 2022 Device CAL do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It grants one physical or virtual device the legal right to access a SQL Server 2022 Standard instance under the Server+CAL licensing model. A Device CAL is a licensing right, not a software component, so there is nothing to install or activate on the database server. Any number of users may work from that single licensed device, which is why it suits shared workstations rather than individuals. It does not include the SQL Server engine itself; you still need a separate SQL Server Standard server license for the machine running the database.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2017-2025-buying-guide-how-to-understand-license-models-cals" target="_blank"><strong>SQL Server Buying Guide - License Models and CALs Explained</strong><br />Walks through Server+CAL versus per-core licensing and how to choose the right SQL product for your user count.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What is the difference between a Device CAL and a User CAL for SQL Server 2022?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A Device CAL licenses a single device for use by unlimited users, while a User CAL licenses a single user across unlimited devices. Device CALs are cheaper when several people share one machine, such as two-shift call centres or a retail floor with shared POS terminals. A 50-person store with 10 shared terminals needs only 10 Device CALs instead of 50 User CALs. User CALs make more sense when staff roam between many devices, for example laptops plus phones plus desktops. Both types can be mixed in the same environment as long as every access is licensed once.</p>
<table style="width: 100%; border-collapse: collapse; background-color: #efefef; margin-top: 15px; margin-bottom: 15px; font-size: 14px; line-height: 1.35;">
<tbody>
<tr><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: left; font-weight: bold; background-color: #dedede;">Aspect</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">Device CAL</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">User CAL</th></tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Licenses</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">One device</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">One user</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Users per license</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Unlimited</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">One</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Devices per license</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">One</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Unlimited</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Best for shift work</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Best for roaming staff</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Mixable together</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
</tbody>
</table>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Who is the SQL Server 2022 Device CAL best suited for?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It is best for environments where many people share a fixed, smaller set of machines that connect to an internal SQL Server Standard database. Shift-based teams gain the most: a warehouse running day and night crews on the same scanners pays once per scanner instead of once per worker. The same logic helps lobby check-in stations, manufacturing-line terminals, and shared back-office PCs. It is the wrong fit for internet-facing applications or unpredictable user growth, where per-core licensing avoids counting clients entirely. As a rough guide, the Server+CAL model stays economical only while access stays below roughly 100–130 users.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does the SQL Server 2022 Device CAL work with older SQL Server versions?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, a 2022 CAL is backward-compatible and can legally cover access to older instances such as SQL Server 2019 or 2017. The governing rule is that a CAL must be the same version as the server or newer, so a 2022 CAL reaches 2022 and earlier servers but an older 2019 CAL cannot reach a 2022 server. This matters during phased upgrades: you can buy 2022 Device CALs first and keep using them as you retire older databases. One CAL also covers access to multiple licensed SQL servers at once, so a single device CAL is not tied to one box. Keep purchase documentation, because CALs are tracked on paper rather than installed and may be requested in a Microsoft audit.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2022-2019-and-2017-features-and-differences" target="_blank"><strong>SQL Server 2022, 2019 and 2017: Features and Differences</strong><br />Compares the recent SQL Server releases so you can match your CAL version to the right server edition.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What should users check before choosing the SQL Server 2022 Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Confirm three things: that your SQL Server is Standard Edition, that you are using the Server+CAL model, and that devices outnumber users. The Server+CAL model is only available for SQL Server Standard, so Enterprise deployments must use per-core licensing and need no CALs at all. Count both direct and indirect access, because devices reaching SQL through a web app, reporting layer, or middleware still require a CAL. If you cannot reliably count devices, or the database is public-facing, per-core licensing is the safer route. Also remember the Device CAL does not include the server engine itself, which is licensed separately.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2017-2025-core-licensing-minimum-requirements-and-incorrect-purchases" target="_blank"><strong>SQL Server Core Licensing - Minimums and Avoiding Wrong Purchases</strong><br />Explains when per-core licensing beats Server+CAL and how to avoid buying the wrong SQL license model.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Frequently asked questions about Microsoft SQL 2022 Device CAL</h3>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Do I still need a separate SQL Server license if I buy a Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes. The CAL is only an access right and grants no server software. You also need a SQL Server 2022 Standard server license for the machine running the database, and the Device CAL is purchased on top of it.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does a Device CAL need to be installed or activated?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. A SQL Server CAL is a licensing right, not a software component, so there is nothing to install or activate on the server. You simply keep proof of purchase to show you hold enough CALs for the devices accessing SQL Server.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can I mix Device CALs and User CALs on the same SQL Server?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, mixing both types in one environment is permitted. The only requirement is that every user or device accessing SQL Server is licensed exactly once, whether through a User CAL or a Device CAL.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Is a Device CAL required for SQL Server Enterprise Edition?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. The Server+CAL model is available only for SQL Server Standard Edition, and Enterprise is licensed per core with no CALs. A Device CAL therefore applies only to Standard deployments using the Server+CAL model.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/buying-guide-sql-server-2017-2025-faq-frequently-asked-questions-about-standard-enterprise-and-ca" target="_blank"><strong>SQL Server Buying Guide FAQ - Standard, Enterprise and CALs</strong><br />Answers common buyer questions about SQL Server editions and when CALs are and are not required.</a></p>