Microstrategy Blog

Ok, this might be amateur stuff here, but you have to start somewhere.

Sometimes the ETL updates conflict with the report cache…so how do you make sure that your users aren’t viewing old data? If your cache is setup to expire every 24 hours, this might create problems for people who subscribe to your reports. There’s the issue of user education (for instance, don’t subscribe to a report at 6 PM if your ETL runs at 11 PM), but the reality is, you’re the administrator, you’re supposed to be able to make the process as simple, painless, and accurate as possible.

Here’s a way you can help move that smoothing process along. Under the administration menu, right click on schedule manager to show the menu listed below.

Select Schedule Administration Tasks, and after picking your project in the next menu, select “Delete Caches” under the option “Choose one of the Following Actions”. Make sure to select which caches you want to delete under the right column “Option”.

It’s as easy as that. Now you can set your report caches to clear after your database load reliably. If the time you want doesn’t exist, then by golly, just make a new schedule.

Reader Atul puts expertness into the mix:

To fully additional automate it you can extend this one step further by

a) Tie an event to Clear the cache using the Microstrategy Command manger event trigger script. Use the ETL tool to trigger the script. Or try to trigger a script by Narrowcast job
b) Schedule the report using Narrowcast and trigger to job execution to recreate report cache.