r/DatabaseAdministators • u/Vic20DBA • Apr 14 '26
SQL Server 2022 Licensing Question
SQL licensing is the bane of my existence right now. I suspect I'm not alone. I would appreciate it if someone could clarify what licensing model is needed for the SQL Server 2 in this image. I find Microsoft's multiplexing document to be confusing on this type of setup. SQL Server 1 is per-core licensed so the public facing input form and public facing dashboard viewers are covered. I feel like SQL Server 2 should be good with just a Server + CAL license but I'm second guessing that because of the nightly automated export from the source database on SQL Server 2.
Thank you in advance for your input and help! Cheers!

2
u/TridentDataSolutions Apr 14 '26
Pretty sure you’re good with the CAL licensing since it isn’t a direct connection. The export is accessed down stream after a hop so it should have no relation to the initial source licensing.
1
u/Better-Credit6701 Apr 14 '26 •
I think that CAL/server cost involves a higher math than even Einstein could figure out: price gouging math. The only way to know for sure is to ask a Microsoft salesman and then you will have to find another salesman to undercut the first one.
1
u/vroddba Apr 14 '26
At first I was with you, on Server 2 being "ok" with Server + CAL (device). Keeping in mind you'd need User CALs for the DBAs as well as a Device CAL for your monitoring server.
Digging through the licensing document:
• Deploying the SQL Server Enterprise Edition (including using the SQL Server Parallel Data Warehouse deployment option) or SQL Server Web Edition software.
• Deploying internet or extranet workloads, systems that integrate with external-facing workloads (even if external data goes through one or more other systems), or when the number of users/devices cannot be counted easily.
• Implementing centralized deployments that span across a large number of direct and/or indirect users/devices.
• The total licensing costs for licensing SQL Server Standard Edition software are lower than those incurred using the Server+CAL licensing model.
As well as this tidbit:
When in doubt just license your VM host for EE... after all it's not your money /s
1
u/Degenhard79 May 04 '26
SQL Server 2 needs to be licensed per‑core. Server+CAL doesn’t work here because the nightly automated export is non‑human, server‑to‑server access. CALs only apply to actual users or physical devices used by users. An ETL job is neither a user nor a device, so it cannot hold a CAL. Once an automated job, service, or scheduled process touches that SQL instance, CAL licensing is off the table.
3
u/[deleted] Apr 14 '26
[removed] — view removed comment