It's all about the answers!

Ask a question

Impact of archiving project area, workitems,... when running a JRS report

jean-claude vauthier (22634856) | asked May 12 '17, 12:26 p.m.


     Does archiving unused RTC project area,  work items and so on improve significantly JRS report execution based on LQE datasource ?

     Does it improve speed of data collection for the datawarehouse ?

     Does it improve JRS report execution based on DW datasource ?

     Does running a repotool deleteJRSResource impact the data collection or JRS report execution performance ?

     Around 5 years of data accumulated.



Kenji Sarai commented May 15 '17, 2:43 a.m.

Hi Jean-Claude,

You mention both LQE data source and DW data source. Which data source are you using now? Generally speaking, archiving project is not helping much because
- DCC or LQE is picking up the data only which has been changed recently
- JRS is usually filtering the data by project at first hand

jean-claude vauthier commented May 15 '17, 2:54 p.m.

Thanks for this answer.

Right now the DW is used with RRDI and several reports are very slow or do not work anymore in a reasonable period of time.   Upgrade to CLM version 6.0.3 is planned using JRS for reporting with both DW and LQE.   We expect better performance, but we wonder if it could not be a good idea to archive old workitems (2012, 2013, 2014,...).

Kenji Sarai commented May 18 '17, 3:31 a.m.

The query in RRDI report (Cognos) and JRS are very different. You need to create a brand new query (report) in JRS, and query in JRS is usually simpler. So it might help, but it all depends on the query you are currently running. You need to elaborate why current query is getting so slow. It might be caused by report design in RRDI, not data size. There is no definite answer at this point.

Regarding archiving projects, if your current reports show data from all projects, then it will definitely help. If only specific project only, then it is not so much.

Be the first one to answer this question!

Register or to post your answer.