Showing results for 
Search instead for 
Did you mean: 

Input ready query performance

Former Member
0 Kudos

Hi Experts,

We are working on input ready queries. But the input ready reports are taking lot of time around 10 to 15 mins to display the results and hence the planning functions like save are also taking lot of time.

We can't use the OLAP cache as these reports are developed on Aggregation level.

Could somebody guide me how to improve the performance of input ready queries.

Thanks in Advance,


Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos


i assume its in the web.

If this is so, it has to do with the script-scanner, even if the application works fine.

Depending on the volume of data it takes with McAffe up to 30 seconds per navigational step.

Solution: Change ScriptScanner from McAffe to Norton or look if you can bypass scriptscan from McAffee for your particular page. If you succeed in the last step, please let me know, because we're facing the same problem.



0 Kudos

Hi Raj,

as I mentioned in another thread, caching happens in the plan buffer (this is also a query), not in the query defined on the aggregation level.

In most cases performance problem (excuse me) come from the application modeling, cf. note 1056259 for background information and a lot of modeling tips.

Note 1083175 may help you to identify the hot spots in your application.



Former Member
0 Kudos


You can do repartitioning and reclustering

Repartitiong help you to partition the cube even after data uploaded in cube.Similar to partitioning but you do after cube load

Reclustering enables related data to be stored in same extent in the database and increase the query performance . Similar to clustering but you do after cube load

There are heap of material available in BI section of SDN which you can make use of


N Ganesh