Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Report is taking too long

Report is taking too long

Report is taking too long

hi I'am new to microstrategy.i would like to know some information about report optimization.
if the report is taking too long,what are the steps i got do?
is ther any specific things i got to do before going to vldb properties?

please let me know


RE: Report is taking too long

1) go to SQL view of the report and check to see if you have any cross joins.
2) Try running the report during off peak hours to see if it still errors.
3) Take the SQL from the report and query your database directly to make sure it's the data retrival that is causing the issue. If the SQL takes faster to execute against the DB directly then it's your Analytical Engine that might be causing problems.

RE: Report is taking too long

If you can get your DBA to review the SQL, they'll probably be able to advise on the most efficient tables/joins to use.  

Try to hit Indexed fields in your attribute ID's (again, check with your DBA if you're unsure which are indexed).

Try to keep attributes simple (ie, don't complicate the functions used on the database elements if you can help it).

Avoid using too many report-end formats, view filters, etc.

RE: Report is taking too long

Keep the report simple

1) Simple attributes, avoid using consolidations or custom groups because they cause multi pass sql sentences and will take up to 3 or 4 times more than the expected

2) Simple Metrics: avoid use metrics with filters in its definition. Each metric with filter in it will generate a diferrent sql pass, is better to use the cross-tab option when you can.

3) When designing a report remember that size of the report is multiply by the number of elements an attribute has that is located on the page-by section, try eliminate o reduce it using filters or prompts.

4) View the Sql to see what fact tables the report is reading an consider maybe generat and aggregate fact table to a higher level so report runs faster.

5) Talk to DBA to see the possibility to generate Partitions over the fact tables you are working.

6) Talk to the final user and try to understand what he is looking for, if the report is generating more than 10,000 lines consider redesigning it (to many information to analyze)

Post your results!! hope this help you!!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close