Wondering if anyone has any insight on if SQL Server 2025 is going to be one of the officially supported Technology Stacks for Kinetic 2026.2 (or even 2026.1)?
We’re interested in some of the features around JSON that it brings for some of our in-house applications.
Thanks!
@timshuwy may have some insight into that officially ( Safe Harbor of course 
).
I know the CR for 2026.1 is out. But not sure if they added SQL 2025 support. With classic ending I could both sides of it. Not spending the time to test and validate SQL 2025 to focus on Kinetic. But could also see them wanting to keep up.
I doubt it will be supported because SSRS is only supported through 2022 and they haven’t released bold reports yet or even said the date for bold reports.
Ah yeah. Didn’t think about SSRS. That will hold up SQL 2025.
I doubt SSRS not being released as part of SQL server 2025 will stop Epicor support SQL server 2025.
As per the reporting services consolidation FAQ SSRS 2022 will continue to be supported until January 2033 and will work with later version of SQL server.
Microsoft reporting services FAQ
Alternatively PBIRS which is available to everyone from 2025 and beyond is practically SSRS and more. And also works with Epicor’s usage of SSRS as a drop in replacement. 
Also, often installation documentation, which states the supported versions, is not up to date until GA. So even if someone 
had access to it through controlled release for 2026.100 it will not be the final documentation until GA.
Wait we just upgraded to 2025 to support our upgrade to 2025.2 on prem did we jump the shark?
Maybe… did you try installing SSRS yet?
The install docs say that OS 22 + SQL 22 OR OS 25 + SQL 22 are certified for v2025.2
We have not. Where would one find said install docs?
In theory it will work fine. You can always set the compatibility level down to 2022 and it SQL will run as 2022. SSRS very likely works too it’s just not officially supported if you have issues.
EpicWeb > Kinetic InstallGuide 2025.2
You’ll have to login to get that with a valid EpicWeb account.
At time I tried trying use report builder it didn’t work that was quite a while ago now though, compatibility might have improved
I’m tested it last year on a training machine. Uninstalled SSRS and installed PBIRS like for like.
Reconfigured Epicor and tested modifying a report. Everything worked as I expected including the SSRS report designer upload / download routine.
I guess we are answering two different questions. I wasn’t saying it wouldn’t work, just that Epicor is not likely to list it in the officially supported stack. That’s what I mean by I doubt it will be supported.
Whereas I do think they will support SQL 2025.
The install documentation etc mention supported SQL server not SSRS and SSRS 2022 is supported by Microsoft until 2033 and work with SQL 2025 and beyond.
Therefore I do not believe that SQL 2025 will not be supported by Epicor just because there isn’t a direct related SSRS. Either use SSRS 2022 or PBIRS 2025.
Only time will tell.
I saw @timshuwy speaking at our Wisconsin EUG yesterday and completely missed the chance to ask him about this. But one thing he did say and present in his slides was about the new release cadence / CI/CD stuff Epicor is moving toward (i.e. there will now only be one “major” version release per year: 2026.100, 2027.100, 2028.100…) The rest of the details were honestly a little confusing, but I did notice that supposedly 2026.100 and subsequent major releases were supposed to be in March, but I haven’t seen anything yet so maybe they’re a bit behind schedule switching over to the new release cadence. Or maybe that only for cloud, not on-prem downloading? Anyone in the cloud confirm or deny that they are on 2026.100 now?
I did ask and was told SQL 2025 may not be officially supported but “should work”.
Works and supported are two different things. When you have an issue and Epicor sees you are using SQL 2025 and say’s “SQL not supported” and closes the ticket then what? I wouldn’t run my production on something that Epicor doesn’t have to support because it’s not officially supported.
