I checked all the docs I could find for all my products while prepping for my upgrade two weeks ago - and I found ZERO official references to SQL 2025. I’m going with the idea that first official support is with 2026.100 release or beyond.
I chose not to try it and set the DB Compat level back to 2022, just on the off chance that the code does something wierd… like that almost never happens…
Well, 2026.100 on-prem downloads are up this morning.
Unfortunately, it looks like SQL Server 2022 is the only version supported:
I did search the Architecture Guide and the Install Guide for SQL Server 2025 and found one odd reference to it in the Install Guide a few pages down from the screenshot above:
That’s a bummer - we’d really like some of the JSON functionality that comes with 2025. But it is one of those things where I’m sure if we used SQL Server 2025 and set the compatibility level on most databases to 2022, it probably wouldn’t break anything, but not sure I’m willing to take the risk.
Truth. I liked v9/10 better when not everything had a risk percentage attached to it.
I wouldn’t in production.
So, you’re not against Progress? 
So subtle I’m not sure how to respond!
You say you would… but have you? 
Has anyone attempted it in production?
I am betting no..
Well we are and slowly going back into the trees now. to see what unholy thing i have done.
You’re running SQL 2025 in production now? Or you are moving that direction with a staging environment?
It’s probably fine and you won’t have any issues. Microsoft is usually good about backwards compatibility. Epicor just won’t officially support it. If you ever ran into an issue they could claim it’s because your version of SQL isn’t supported and not offer support for your issue. Then what do you tell the business?
I just don’t see a reason to do it in production. SQL 2022 is fully supported by Microsoft.
And there would be no reason not to run using the right compatibility either… Just my 2c
