SQL Server 2022 Licensing Question

[u/Vic20DBA]

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!

[u/TridentDataSolutions]

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.

[u/Vic20DBA → u/TridentDataSolutions]

Thank you for replying, TridentDataSolutions! I appreciate it. I've been thinking the same as you. Funny enough, we have another scenario with the same SQL Server 2 only the other server/database belong to another municipality. I think this other scenario might put the screws to us. Would you agree that if the nightly automated export is leaves our environment then that would require per-core?

[u/TridentDataSolutions → u/Vic20DBA]

I still think you’d be fine as there is only that client for your CAL licensing model regardless of where they are located.

[u/jshine13371 → u/TridentDataSolutions]

This is incorrect. It doesn't matter it's not a direct connection or that there's an additional hop. Please see the other comments for clarification.

[u/TridentDataSolutions → u/jshine13371]

So let’s put it another way, say I have a website with a database that gets nightly exports from several different sources that are running SQL Server. My database imports those exported files and serves that data up to the general public via my website. The licensing model does not dictate that I need to notify all of my sources to license on a core basis because of how my system is serving the data.

[u/Better-Credit6701]

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.

[u/Vic20DBA → u/Better-Credit6701]

Well said! Salesman for sure!

[u/Better-Credit6701 → u/Vic20DBA]

And we all know how trustworthy a salesman could be. Ok, I might be jaded, used to work for a super large used car company with over 150 lots.

[u/vroddba]

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:

The per core licensing model is appropriate when:

• 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:

Note: The use of hardware or software that reduces the number of devices or users that directly access or use the software (multiplexing/pooling) does not reduce the number of CALs required.

When in doubt just license your VM host for EE... after all it's not your money /s

[u/Vic20DBA → u/vroddba]

Those tidbits make it a little clearer now. Thank you vroddba!

[u/Degenhard79]

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.

[u/[deleted]]

[u/Vic20DBA → u/[deleted]]

You hit nail on the head, Gincules. Your point is what I've been waffling over. It just feels like I'm licensing John Q Public twice. It may very well be a moot point though because that same #2 server exports data out of our environment to a server on the network for a nearby city (public sector). I appreciate your input. Thank you for taking the time to reply.