Explainer
SQL Server CAL count for historian clients: how to size it
Short answer
SQL Server CALs attach to the people and devices that reach SQL Server, not to historian client sessions or pooled connections. Trace every SQL access path - historian server services, collection nodes, trend and report clients, embedded controls - to its users and devices, count both populations, and buy whichever count is smaller. The historian's tag count, even 25,000 tags, sets neither the SQL edition nor the CAL total.
On this page
- How many SQL Server CALs does a historian need?
- Why doesn't the historian client list match the CAL count?
- Does a 25,000-tag historian need SQL Server Standard?
- Which components must you trace to SQL access?
- Should you buy user CALs or device CALs?
- Can per-core licensing remove the CAL count?
- Do historian licenses already include SQL CALs?
- How do you turn the inventory into a purchase?
- Questions asked
A historian writing to SQL Server does not create one SQL Server CAL per connected client. Microsoft licenses SQL Server access per distinct user or per distinct device, so the CAL total is either the count of people who can reach SQL data or the count of machines that reach it - whichever basis you purchase.
The two views plant engineers reach for first both count the wrong thing: the historian console's client list shows live sessions, and SQL Server's connection view shows pooled connections from a single service account. Neither names the endpoints the license follows. The working method is an inventory: list every component that pulls from or pushes to SQL - the historian's own services, remote collection nodes, trend and report clients, embedded trend and alarm controls, SQL-based reports, engineering tools - resolve each to its users and devices, count both populations, and buy the smaller count. Tag totals never enter the arithmetic.
How many SQL Server CALs does a historian need? #
Count the distinct people or the distinct machines that can reach SQL Server through any path the historian opens, then buy the smaller count: 18 people on 16 machines plus the historian host means 17 device CALs, not 18.
A SQL Server CAL is an access entitlement, not a piece of software and not a session slot. Microsoft's Server+CAL model offers two bases: a user CAL covers one named person, and a device CAL covers one machine, however many people share it. Either basis covers access to all of your SQL Servers, and the two are never added together for one server. The requirement is that every person, or alternatively every device, that reaches SQL Server is covered, so the purchase is simply the smaller of the two populations.
That reframes the question from 'how many clients are connected' to 'who and what can ever get to the data'. A historian feeding a quiet control room can need fewer CALs than one serving a reporting-hungry office, purely because of who reads the data.
Why doesn't the historian client list match the CAL count? #
The historian's client list and SQL Server's connection view both count live sessions, while the license counts endpoints, so a hundred trend clients behind one pooled service account still need a hundred CALs.
Two displays mislead in opposite directions. The management console's client list is operational: it shows which clients currently talk to the historian, not which of those paths end at SQL Server, and not the people who will log in on the next shift. SQL Server's own connection view flatters the count for a different reason: a historian multiplexes its clients through pooled connections under one service account, so twenty viewers can appear as a single login from the historian's host.
Microsoft's rule places the requirement at the endpoint of the access. When clients reach SQL Server through an application in between - and a historian is exactly that - each distinct user or device behind the application needs coverage, and the pooled connection count never enters the calculation. One historian vendor states the identical rule in its own documentation, where server's CAL count follows every user and device that touches it.
Keep the connection view for what it does well - diagnosing load and spotting a stuck query - and take licensing numbers from the inventory in the sections below.
Does a 25,000-tag historian need SQL Server Standard? #
No - a tag count, whether 25,000 or far higher, sets neither the SQL edition nor the CAL total, because a historian keeps its time series in its own compressed store and leaves SQL holding configuration, summaries and the tables the client applications query.
The historian writes its block data to its own archive; SQL Server carries the metadata and the tables that trend clients, report generators and similar applications read, plus the historian's internal store-and-forward queue. What stresses SQL is concurrent query volume from those consumers, not the size of the tag list.
Judge the edition on that load. Most historians publish system tags for SQL Server processor load, memory use and page faults; watch them for a week of production traffic. Quiet readings mean the current edition keeps working; pressure from concurrent clients is the reason to move up. Express edition limits themselves - database size, memory - differ between SQL Server releases, so read the documented limits for the exact release you run. No step in this converts the tag total into a CAL quantity or an edition requirement.
Which components must you trace to SQL access? #
Trace every component that reads from or writes to SQL Server, directly or through the historian: the historian server's own services, remote collection nodes, desktop and web clients, embedded trend and alarm controls, SQL-based reports and the engineering tools your team opens.
| Component or access path | Resolve it to | What it adds to the count |
|---|---|---|
| Historian server and its local services | The historian host machine itself | A device CAL on the historian server covers its local SQL connections and internal queues |
| Remote collection nodes | Each node device, plus the staff who configure it | One device CAL per node, or user CALs for those staff |
| Desktop and web trend clients | Every person who logs in and every machine they log in from | Concurrent-seat capacity is ignored; distinct people and machines are counted |
| Embedded trend, alarm-history and summary controls in the HMI | The station device and its users | The control is another SQL path; its endpoint still counts |
| SQL-based reports | The machine that runs scheduled reports; the person who requests interactive ones | Scheduled runs add the report host; interactive runs add the requester |
| Query and profiling tools | The engineering workstation | Usually one device CAL per engineering bench |
A panel PC that skips the historian and writes its own records to SQL Server is a separate access path with its own endpoint: the setup in logging production data from a panel PC to SQL Server puts that panel PC on the device list. The same holds for an OPC-to-SQL logger - in a setup like logging PLC values from an OPC server into SQL Server, the logger's host machine is the device touching SQL.
Should you buy user CALs or device CALs? #
Buy whichever population is smaller: device CALs when people outnumber machines, user CALs when they do not - in the worked example below, 17 device CALs beat 18 user CALs by one.
A device CAL wins wherever people share machines: a terminal used by six operators costs one device CAL instead of six user CALs. A user CAL wins wherever one person roams: an engineer with a desktop, a laptop and a phone costs one user CAL instead of three device CALs. A concurrent-seat limit on the historian's client licenses is neither a shortcut nor the SQL count: a web client capped at 10 concurrent users, actually used by 25 people from any of 15 workstations, still needs 25 user CALs or 15 device CALs - and 15 is the buy. When a seat ceiling trips, that is the client product's own license failing; the failure and its fix look like a maximum licensed clients error on a SCADA client.
Worked example, with illustrative counts for one line historian:
- 12 operators share 8 panel-PC trend clients.
- 4 engineers each use an office desktop and a laptop.
- 2 managers read scheduled reports issued from 1 shared office PC.
User count: 12 + 4 + 2 = 18 people, so 18 user CALs. Device count: 8 + 4 + 4 + 1 = 16 machines, plus the historian host as a device makes 17, so 17 device CALs. Because 17 is below 18, buy 17 device CALs.
What moves it: every extra distinct device adds one to the device total and every new person adds one to the user total. If two engineers also open trends from their phones, devices rise to 17 + 2 = 19, which passes 18, and the basis flips to 18 user CALs. The crossover sits at (users - devices) extra devices - here 18 - 17 = 1 - so the second extra phone tips it.
Can per-core licensing remove the CAL count? #
Yes - licensing SQL Server per physical core grants unlimited users and devices with no SQL CALs at all, which makes it the branch to price when the inventory produces a large user or device count on a small number of cores.
Under the Server+CAL model you buy the server license once and cover every endpoint with CALs. Under per-core licensing you buy all physical cores on the server and the endpoint counts disappear from the purchase entirely. The same inventory serves both branches: it yields min(users, devices) for the CAL branch and the raw population for the comparison against your core count in the core branch. A plant where hundreds of people and stations touch SQL usually lands on per-core; a handful of control-room stations usually lands on CALs. The two are alternatives for the same server, not add-ons to each other, and the comparison runs on your own counts.
Do historian licenses already include SQL CALs? #
Some older historian bundles shipped with SQL Server Standard and the matching SQL Server CALs included, so audit your purchase and license records before buying anything: the entitlements may already sit in your license file.
Read the exact edition and line items on the licenses the plant owns. Where SQL entitlements appear, subtract them from the inventory total instead of ordering duplicates. Where they do not, plan the SQL Server installation like any other licensed software on an industrial edge PC and then buy CALs to match the count you derived. Do not infer an entitlement from a product family name or from a previous project's paperwork; the entitlement follows the specific licenses the plant holds.
How do you turn the inventory into a purchase? #
Six steps decide it: inventory every SQL access path, resolve each path to people and machines, count both populations, buy the smaller count as user or device CALs, verify existing entitlements against the records, and only then judge the SQL edition from measured query load.
- List the access paths. Use the table above as the checklist and add plant-specific writers such as panel-PC loggers and OPC gateways.
- Resolve every path to identities. For each path, write down the people who use it and the machines it runs on; include the historian host as a device.
- Count both populations. Distinct users U, distinct devices D.
- Buy the smaller. min(U, D) CALs of that type - 17 device CALs in the worked example - or switch to per-core licensing when the population is large against the core count.
- Audit entitlements. Match existing SQL Server licenses and any SQL rights bundled with the historian before ordering.
- Verify the edition on load, not on tags. Watch the historian's SQL system tags for a week of production traffic; move to Standard only for measured query concurrency.
The decision in one line: SQL Server CALs equal min(distinct users, distinct devices) that can reach SQL Server through the historian and its neighbouring paths, purchased in whichever type is smaller - and the 25,000-tag figure sizes the historian, never the license.
Questions asked
Does one SQL Server CAL cover access to several SQL Servers?
Yes. A SQL Server CAL is an access right to the SQL Server software, not to one named installation. Under Microsoft's licensing terms, the user or device CALs you buy to cover historian clients also cover the same people or devices reaching other SQL Servers in the plant, so one purchase can serve several servers.
Do you need SQL Server CALs if the historian runs on SQL Server Express?
No. SQL Server Express is free to deploy under Microsoft's licensing and requires neither a server license nor CALs; its constraints are technical caps on database size, memory and processor use that change between SQL Server releases. The CAL arithmetic in this article applies once the workload pushes the installation to Standard.
Do read-only report viewers still consume a SQL Server CAL?
Yes. Microsoft's CAL model counts every distinct user or device that receives SQL Server data, directly or through an application such as a report server, and read-only access is still access. The exception is per-core licensing, where no per-viewer count exists at all.
Are Windows Server CALs the same as SQL Server CALs?
No, they are separate licenses with separate counts. The Windows Server installation that hosts SQL is licensed under Microsoft's Windows Server terms, typically with Windows Server user or device CALs, and that population is counted and purchased separately from the SQL Server CAL total, even though both follow the same user-or-device idea.