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

[L.Elias]

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)

[Jon_Israel]

Hi Lino,

You bring about a great question.  Unfortunately the version of SQL that Jasper is certified with is up to Tibco and not CA as we dont make the Jasper software.  Currently Tibco only supports SQL 2012 and 2014 with Jasper 6.4.x.   So in your case, if you dont want to use two separate database instances, then your only option would be to create a new instance using SQL 2014, and then as you mentioned, upgrade that later on when needed.

Outside of that the only option is to use two separate SQL instances.

I cannot think of any other way to do this.

Jon I.

[Suman Pramanik]

Adding to what Jon said we did ask Jaspersoft to certify that. Once we hear back we will let you know. 

[L.Elias]

I understand that what Jaspersoft supports is out of CA's control, but selecting Jaspersoft as the official reporting component was, as was CA deciding not to support SQL 2012 while both Jaspersoft and Microsoft (via extended support) both continue to support 2012. If CA also continued to support 2012, none of this would be an issue. Having different components requiring different things over complicates matters.

 

I really try to push for frequent app updates but in a generally slow moving organization like mine this is the sort of thing that gets people to toss up their hands and say "well we'll just stay with what we're on instead." If CA really wants people to remain up to date, they need to take these sorts of things in to account.

[Suman Pramanik]

Hi Lino,

 

We definitely understand your concerns and we are working with Tibco and trying to get MS SQL 2016 supported. The targeted timelines are about 3 months.

 

Regards

Suman Pramanik 

[Juan Vizcarra]

Hi. We have struggled with this too.

We noticed that CA has published EOS for Jaspersoft 6.2.1 and should migrate to 6.4.2

 

But, Jaspersoft 6.4.2 does not support SQL 2016 Server either

(Source: CA PPM 15.4 Release Notes - CA PPM - 15.4 - CA Technologies Documentation )

 

So, if 2016 support is on the roadmap, I think we will have to wait.