Report Caches Overview and Best Practices

MicroStrategy report caches store all report results in I-server for fast retrieval. They reduce the response time to bare minimum as compared to the reports that execute against cubes, aggregate tables, or fact tables on the data warehouse.

Understanding Caching and Recommended Best Practices!

This week is dedicated to Caching! The goal is to learn the following:

• What is caching
• How does caching work?
• Different types of caching 
• Recommendations for optimizing Caching for Hi performance results 

Microstrategy SQL Engine Framework!

MicroStrategy engine is the brain of the whole system, no exaggeration!. It consists of 3 individual engines that work in tandem to fulfill report requests submitted by MicroStrategy desktop, MicroStrategy Web and other MicroStrategy products

How to repeat column values on every row of the grid?

Even though it seems like the most simplest things to do, trust me it is really hard to find the setting that does that.

MSTR 9.3.1 Bug - Error handling option to deliver document upon "No data returned" does not work

If you don't want distribution services to deliver emails when there is no data returned for a report or document, then you can do that by changing the error handling setting in Project configuration.

Project Configuration -> Deliveries -> Error Handling

You can change this delivery option for both partial and no data results.

However, currently, this setting only works for reports and not for documents.

This is a known issue with MSTR 9.3.1, logged in TN32763, and is stated for a fix in the next MSTR release.

Nonetheless, there is a workaround that can be used for documents, shown in TN34054, which is nothing but creating an alert subscription on the report, to only send out email when the document contains data with some value.

3 different ways to maintain caches to ensure up-to-date data

Creating and maintaining caches is an important part of effective Microstrategy environment management. It not only improves Microstrategy speed by fast retrieval of reports, but also reduces the load manifolds on the warehouse, and network, thereby improving overall system performance.

However, it is equally important to make sure data is always as up to date as the user would like it to be.

How to get Personalization to work in Dynamic Recipient List in MSTR 9.3.1?

Dynamic recipient list is a great new feature in MSTR 9.3.x and I think is extremely useful. It adds the capability of sending user specific personalized data for email delivery.

TN41561 explains in detail how to set up dynamic address recipient list 9.3.x. You should have the option of setting it up in web under User preferences. In case, you don't find the option, then please refer TN41710.

However, in order to get the user personalization to work, you have to populate the personalization column of your dynamic recipient table with the necessary PROMPTXML data for each of your users in the table.