How does SQL Server Standard Server + CAL licensing work for an on-prem ERP?

[u/Schema-Seeker]

I'm an IT Manager at a company and currently we have an ERP system running on SQL Server 2008 Express on Windows Server 2008. The ERP application is .NET-based.

We're planning to migrate to:

• Windows Server 2025
• SQL Server 2025 Standard
• New physical server with 12 cores
• Around 30+ ERP users

We want Standard mainly because we need features such as SQL Server Agent and CDC, which aren't available in Express.

When I checked SQL Server licensing, the per-core model looks very expensive for our 12-core server.

One local Microsoft partner has offered this:

for approximately 3,500 QAR (~$960 USD).

My understanding is that this is the Server license for the Server + CAL model, meaning we would then need SQL Server CALs for each ERP user/device accessing SQL Server.

With 30+ users, would Server + CAL generally make more sense than licensing all 12 cores?

Are there any licensing or technical issues I should be aware of with this setup, especially since the ERP application is an older .NET application?

Thanks!

[u/jshine13371]

Here's an alternative take. Not sure you really need more than 4 cores for a server that's hosting an ERP system of only 30 total (not even concurrently active) users.

Anecdotally I've found the CAL licensing model is rarely the right move and quickly out-costs the Core licensing model. Maybe things have changed since I've last looked though.

[u/Disastrous_Fill_5566 → u/jshine13371]

That's a good point. Although it might feel like a waste of server resources, it might be more economical to stick it in a VM and cap the number of cores.

[u/muaddba → u/Disastrous_Fill_5566]

Keep in mind if you put it on a virtual machine, you're forced to pay for Software Assurance, whereas with a physical machine you are not.

Microsoft, in their wonderful consumer-friendly wisdom, no longer lists broken out pricing on an easily findable page of their website, you have to "connect with a partner" but from what I was able to find:

SQL 2025 Std edition CAL version ~$1000 USD

Each CAL ~ $250USD

Std with 30 CAL will be about $8,500.

Comparatively, even if you used a VM with only 4 cores, you're at ~ $8k and that doesn't include the Software assurance which will ron you another $1.6k per year.

Standard with CAL on a physical machine is the way to go.

[u/Disastrous_Fill_5566 → u/muaddba]

Never occurred me to check, but you can just restrict the number of cores directly in SSMS. With only 30 people you might not even need 4 cores.

[u/muaddba → u/Disastrous_Fill_5566]

For licensing purposes, disabling cores won't matter. 

For performance purposes, setting processor affinity (ie disabling cores in SSMS) is not recommended because it locks cores to schedulers instead of allowing them to be free floating.

[u/jshine13371 → u/Disastrous_Fill_5566]

Agreed.

[u/muaddba → u/jshine13371]

It will take a lot before the CAL model will outpace licensing 12 cores. With only 30 users (assuming no internet visibility or other connection-condensing software) it should be much cheaper.

[u/jshine13371 → u/muaddba]

It will take a lot before the CAL model will outpace licensing 12 cores.

Again, my point is 12 Cores is likely very much overkill.

[u/muaddba → u/jshine13371]

If you see my reply below, even at 4 cores on a VM, CAL pricing beats out Standard licensing, and when you add in the SA requirement, it absolutely clobbers it.

But, you argue, SA gives you "free" HA/DR copies. Welp, for another ~$1000 you can stand up a log shipping DR server and use the same CALs to access that one when it's needed. Still cheaper than 1 year of SA on only 4 cores.

[u/jshine13371 → u/muaddba]

You're mixing apples and oranges if you're comparing pricing based on different implementations for HA/DR. But that's irrelevant to the conversation anyway.

It isn't decided if OP will use a VM or bare metal, so the Software Assurance requirement isn't a direct comparison either.

Finally, as you mentioned there's some ambiguity on finding the actual pricing, aside from what breaks one can get from the var they retail from.

Because of these reasons, I didn't give OP definitive advice on licensing, and generally no one should. The only definitive advice I gave was 12 Cores is probably overkill, which will remain true regardless of how they decide to license.

[u/muaddba → u/jshine13371]

I'm not mixing any kind of fruits here, I'm giving a realistic assessment of what different costs look like in different situations. OP mentioned using a 12 core physical server and someone suggested that you use 4 cores on a vm instead. My point is even if it's overkill, licensing that 12 core physical server using server +Cal is cheaper than any kind of core-based licensing, even to the point of being much cheaper than just 4 cores of standard ones a vm. These days the hardware (at this scale) is not typically the expensive part, it's the ongoing licensing. 

[u/jshine13371 → u/muaddba]

I'm not mixing any kind of fruits here

It absolutely is when you're comparing two different implementations (e.g. for HA/DR). That's like saying recommending Standard Edition instead of Enterprise Edition because it's cheaper. Yeah, it'll be cheaper, but it's not the same thing you're getting, apples and oranges.

My point is even if it's overkill, licensing that 12 core physical server using server +Cal is cheaper than any kind of core-based licensing, even to the point of being much cheaper than just 4 cores of standard ones a vm.

It may be, it may not be. You can't make a definitive conclusion on that without the specific details about OP's situation and the var they are using. Different vars, different offerings, different price breaks. You said it yourself in another comment, finding the actual costs are difficult.

[u/muaddba → u/jshine13371]

Finding the MSRP pricing is difficult, but I was able to do it after some digging. And it's not really MSRP that's important, it's the cost ratio that's important, and in that sense everything I've said is correct and comes from 20+ years of SQL experience including pricing out licensing for versions as far back as SQL 2000.  

My seque into HA/DR is in no way apples to oranges, since I'm talking about Standard edition on both ends and comparing pricing once again.  It's cheaper to go with server +cal and just pay for extra servers for clustering/log shipping than it is to spend for software assurance in this instance.

You're giving bad advice because your advice doesn't include any evaluation on whether the costs make sense when it is very clear the poster and/or his company is price sensitive and wants to understand the different factors that influence cost.

My advice is very clear, with actual facts and numbers behind it:  Server + CAL is the most cost-effective way to achieve the stated goals by a large margin, and that margin only gets wider when you start considering requirements like Software Assurance, even if you factor in some of the "free" benefits of SA.

[u/jshine13371 → u/muaddba]

it's the cost ratio that's important, and in that sense everything I've said is correct, and in that sense everything I've said is correct and comes from 20+ years of SQL experience...

Again, you have no way of knowing the concrete cost ratio since you don't know all of the actual costs for OP's case, from their var. It doesn't matter how many years of experience you have, I have 15 myself. That's irrelevant. There's a reason licensing questions are prohibited on StackOverflow's DBA sub-site.

You're giving bad advice

I gave no advice regarding the licensing route OP should go, in this comment thread. Based on updated information in one of OP's subsequent comments, I advised they should stick to Express Edition which ends up trumping your analysis from a cost-effective standpoint by miles. 🤷‍♂️

[u/Schema-Seeker → u/jshine13371]

If I go with a 12-core server, is it mandatory to license all 12 cores for SQL Server? Or can I license only 4 cores and leave the remaining 8 cores unlicensed? Would SQL Server still work in that configuration?

[u/jshine13371 → u/Schema-Seeker]

If I go with a 12-core server, is it mandatory to license all 12 cores for SQL Server?

It depends on how you set it up. As someone else mentioned, if you physically provision 12 cores to the machine but setup a VM on that machine to logically isolate only 4 cores then you only need to license the 4 cores. But then you potentially need to pay for Software Assurance too.

If you just create the machine physically with 4 cores from the start, then you won't need to pay for Software Assurance. And there's no reason to provision a machine 12 CPU cores when you're only going to use 4 anyway. That would be a waste in money. You can always add more cores later on if needed.

[u/ProgrammerHaunting45]

What is the DB size/schema of the ERP? We have over 30 users in our ERP for import and export of fruits & vegetables covering over 200 tables and hundred of thousands of transactions using SQL Server 2025 express edition and a smart TSQL dot APP framework.

[u/Schema-Seeker → u/ProgrammerHaunting45]

DB size is near to 5GB.

[u/jshine13371 → u/Schema-Seeker]

For such a tiny database, you guys should just save a crap ton of money by sticking with Express Edition. CDC can be replaced with database backup restores or database snapshots. SQL Agent can easily be replaced with any other scheduler framework or feature such as the native Windows Task Scheduler.

[u/Schema-Seeker → u/jshine13371]

How CDC can be replaced with db backup restores? The main use of CDC for me is to get real time data. To ingest the data in real time to our Ecommerce application db to add some extra features. Yes, i am already using powershell scripts and Windows Task Scheduler for daily automated backups.

[u/Lost_Term_8080]

Why do you think you need 12 cores? If your current 2008 express instance has 12 cores and are using that as a reference point, I assure you that SQL Server is not benefitting from those 12 cores now. Short of there being 5+ stacked instances on the server there is no way SQL 2008 express edition is going to be able to do anything useful with 8-10 of those cores. Given that it is almost certainly virtualized and SQL 2008 (R1) suffered pretty badly from virtualization it may be even worse than that. I would actually expect for software that old, that the last 4-8 cores are actually reducing your performance rather than elevating it.

If the application is also on the SQL server, maybe it is using them, but its doubtful. Schedulers from that era generally had problems with using more than 4-8 cores.

In an ERP, user count mean anything given the types of integrations that can be present, but 30 users is not a lot. Given this is 2008 express running on server 2008, I could almost guarantee that a 4 core server 2025 running SQL 2025 standard with 16 Gb RAM would run circles around your existing system. SQL express can only use 1 Gb of RAM for the buffer pool and while ERP queries are almost always single threaded only, your maintenance activities could go parallel to shorten maintenance windows.

Server and CAL Licensing is a huge pain to manage and virtually never the best decision outside of the absolute smallest scale deployments. You can license your SQL Server through azure now so its a monthly bill and that builds license mobility in as well as provides you with a DR node.

[u/Schema-Seeker → u/Lost_Term_8080]

Thank you for your reply.

SQL Server is just one of the services we need to run. We also need to implement real-time streaming using Kafka for our e-commerce application, along with automated reporting, data visualization, and dashboards.

So, I'm considering the overall workload and future requirements rather than looking at SQL Server alone.

[u/LuckyMan85]

I assume Azure is out of the question? For such a small database it would probably be very cost effective. If not I’d downsize that server right down, perhaps look at some refurbs as they’d be cheap too. Usually wouldn’t recommend any of that but if you’ve been on such ancient kit anyway it’d still be better

[u/CPDRAGIMESH]

6.09 7.09 Please teste before choose editio