Performance of Impromptu Reports

[cogjai]

Hi
We are doing a project for a clinet in Impromptu reports. We are facing performance issue problems. Shall any one suggest any performance improvement measures we can generally follow in Impromptu.

thanks in advance

 

[DoubleD]

First we'll need to know what database you're running against. Next we'd need to know some specific examples.

The only suggestions I can make without specifics are as follows:
1. Push as much processing as possible to the database. Use the database functions when possible instead of the Impromptu based functions.
2. Avoid summary filters as they almost always run locally.
3. Ensure the database has the appropriate indexes set up to accomodate your most common filters.
4. If you are running against Oracle, use Decode instead of If Then Else whenever possible.

Pain is stress leaving the body

DoubleD

 

[Exie]

.. If you have issues building Cubes from IQD's, I usually copy the SQL and run it through an optimiser such as TOAD, I've seen some significant improvements in the SQL code and in turn the cube building performance.

 

[stewm]

Takes a good long look at your database. Try to do as much as you can in the database upfront. Setup your reporting environment to maybe report as far back as yesterday. That way you can create a datamart and refresh it over night. This way the joins and all that extra stuff gets done at night at 3am or something. Get the heavy weight stuff out of the way before the business day starts. After you get the data you want your reports should take one second to one.



Mark Stewart
Consultants Club Corp.