<p>I am looking for a way to re-use or cache the rows returned by a query in a report for Maximo 7.5 so that each object bound to the data set (table, cross-tab, chart, etc.) does not re-run the query against the database. I would prefer that subsequent calls to the data set returned by the query be against some kind of cached data set, array, etc. </p>
<p> </p>
<p>Most of the reports in my library for Maximo use a single query producing a data set. The data set in many of these reports is used more than once (bound to more than one object). It seems that when these reports are run in the BIRT designer on my desktop, the query is run once and the data set rows are cached and reused by the report objects. I believe this because the average time to execute the report query externally in a database tool like Oracle SQL*Plus is about the same as the total report execution time in BIRT. When the same report is run in Maximo with few or no other reports in the processing queue, it takes a lot longer. The report run log files both in BIRT and in Maximo confirm the query is being executed once for each bound object in the report when the query returns rows.</p>
<p> </p>
<p>Best practice of course dictates that report queries should be optimized before deployment, but some queries are inescapably more complex and take longer. I can also minimize repeat calls to the data set in some, but not all reports. That leaves me with the need to find a way to re-use data sets without re-querying the database each time.</p>
<p> </p>
<p>Any suggestions would be greatly appreciated.</p>
