Epicor 10.2.x SQL Server Runtime

We were considering an upgrade to 10.2.700, but our current SQL Server 2014 which is not supported.

Epioor Support had mentioned that staring this year, they are including a SQL Server Runtime version which could be purchase under a Maintenance Contract.

I had never heard of such a thing and just curious if anyone out there is using it and what are the issues if any? I cannot find any technical information about this.

This is what we have done Tom. It’s a run-time version only, so no other applications should be running on it. There is maintenance that gives you upgrade privileges in the future. They started this years ago. It is not new this year.




Thanks for the reply. Quick question for you: We have 2 customizations that use a scheduled SQL Job to schedule and automate some DMT templates and then uses DB Mail to send out notifications if those were successful or failures. Does the SQL Runtime allow the ability to use SSMS and also SQL Jobs? If so, then this could be a viable solution sine the user base is only 15-20 Users.

Definitely use SSMS (or Azure Data Studio - which works on all SQL Servers, on prem or otherwise). I’m pretty sure we’re using SSIS and emailing stuff too. I don’t know about jobs.

Also using the runtime version, and have always done so across 2 companies using Epicor since 2015. There are no feature restrictions, same functionality as SQL Standard. It’s only license conditions which you have to comply with.


I have been chasing this issue with Epicor Support and the CAM for weeks now and they cannot seem to give me any information on SQL Runtime.

All I can assume is Great Plains does a similar thing and it stipulates the following per their well-written documentation.

1.) No other 3rd-party databases can be installed inside the licensed instance. Only the ERP databases can be used.
2.) CAL licensing applies to SQL depending on the CALs for the ERP software. If you have 50 Epicor CALs, then the number of CALs cannot exceeded this in SQL.

Per the previous comments, it appears SQL Runtime is just like Standard but with those 2 aforementioned licensing restrictions.

Can someone please confirm if this sounds correct?

That is how I understand it as well. It is for Epicor products only. The CALs may be different as you might have more connections than user CALs with services, etc. also running. But the spirit is what you wrote.


This is what appears on my Epicor Maintenance Invoice. I went for CORE licenses, rather than CAL licensing. Like I said before though, been doing it for years so the offerings from Epicor today may differ.

You’re correct in what you say, it’s only a license limit for you to self-enforce rather than electronic licensing mechanism.

1 Like

The devil is in the details I guess. Googling I came across this Third Party Terms | Epicor U.S.

" A Microsoft SQL Server “runtime” license may not be used to develop new applications, databases, or tables for non-Epicor supplied applications."

I don’t think I saw bartender mentioned, it comes with SQL express.

1 Like

If you are somewhat a medium - large business chances are you have some kind of licensing deal from Microsoft, check into that too. We had some kind of Enterprise licenses, which lets you install as many Hyper-V’s as you want, SQL Servers etc…

Now we use SQL Enterprise because we want to consume more than 4 Cores, super-fast Epicor! Always On Availability etc…

And you can move them into Azure and not have to pay extra!


1 Like

In the “spirit” of licensing all that is mentioned is correct. Maybe some examples will clarify it.

  • Runtime is for E10 apps and you get upgrades as long as you are in maintenance on it. It is very cheap compared to SQL standard but has mostly the same functionality
  • Epicor has allowed 3rd party apps to use the same db server. For example, BizInsights, SmartForecast, Budget Maestro.
    -If you want to create a db for log phone server activity or an in house developed solution, there is no restriction, but this violates the EULA.
  • The murky area is tables/db that are created for integrations. They are using supplied Epicor applications (on one side).

We have never had a support person or consultant say the murky area is outside the EULA. What they are trying to keep you from doing is to use it as your SQL db for every other non Epicor application

1 Like