AnsweredAssumed Answered

How are you handling inconsistent PPM vs DWH SQL Server requirements?

Question asked by L.Elias Champion on Apr 3, 2018
Latest reply on Jun 20, 2018 by juanv

Currently we are running 15.1. Our Jaspersoft usage is extremely light so we have both PPM and DWH databases on one SQL 2012 server. We are beginning to plan moving to 15.4, but have hit a bit of a snag. PPM 15.3+ support SQL 2014 and 2016, while Jaspersoft support 2012 and 2014. Initially we were planning to do a simple in place application upgrade to 15.4 for now, and do a full upgrade to Windows and SQL 2016 on our next upgrade, but with SQL 2012 not being supported for PPM, no longer have that option. I did reach out to support since our organization is under extended support for SQL 2012 from MS which doesn't end for quite some time, hoping that would somehow give us on out to continue using it, but that was a  no go.


Is anyone else struggling with this sort of issue or is everyone else running PPM and DWH on separate database servers? It seems our only options at this point are to upgrade our DB to 2014, just to probably have to upgrade it again to 2016 next year, which feels unnecessary, or to put off upgrade until Jaspersoft supports 2016, which there is no guarantee that the next PPM release will bring a compatible Jaspersoft before 15.1 is EOL. (Technically additional options would be to go to 15.2 which is pretty pointless, or seperate PPM and DWH databases at additional expense, but neither of those are viable)