Types of result caches in Microstrategy

Types of result caches Microstrategy

The following types of result caches are created by Intelligence Server:

•

Matching caches

•

History caches

•

Matching-History caches

•

XML caches

All document caches are Matching caches; documents do not generate History caches or XML caches. Intelligent Cube reports do not create Matching caches.

Matching caches

Matching caches are the results of reports and documents that are retained for later use by the same requests later on. In general, Matching caches are the type of result caches that are used most often by Intelligence Server.

When result caching is enabled, Intelligence Server determines for each request whether it can be served by an already existing Matching cache. If there is no match, it then runs the report or document on the database and creates a new Matching cache that can be reused if the same request is submitted again. This caching process is managed by the system administrator and is transparent to general users who simply benefit from faster response times.

History caches

History caches are report results saved for future reference in the History List by a specific user. When a report is executed, an option is available to the user to send the report to the History List. Selecting this option creates a History cache to hold the results of that report and a message in the user’s History List pointing to that History cache. The user can later reuse that report result set by accessing the corresponding message in the History List. It is possible for multiple History List messages, created by different users, to refer to the same History cache.

The main difference between Matching and History caches is that a Matching cache holds the results of a report or document and is accessed during execution; a History cache holds the data for a History List message and is accessed only when that History List message is retrieved.

For more information about History Lists, see Saving report results: History List.

Matching-History caches

A Matching-History cache is a Matching cache that is referenced by at least one History List message. It is a single cache composed of a Matching cache and a History cache. Properties associated with the Matching caches and History caches discussed above correspond to the two parts of the Matching-History caches.

XML caches

An XML cache is a report cache in XML format that is used for personalized drill paths. It is created when a report is executed from MicroStrategy Web, and is available for reuse in Web. It is possible for an XML cache to be created at the same time as its corresponding Matching cache. XML caches are automatically removed when the associated report or History cache is removed.

To disable XML caching, select the Enable Web personalized drill paths option in the Project definition: Drilling category in the Project Configuration Editor. Note that this may adversely affect Web performance.

Comments

Fact tables levels tables in Microstrategy explained

Fact tables levels in Microstrategy: Fact tables are used to store fact data. Fact tables should contain attribute Id's and fact values which are measurable. All the descriptive information about the fact tables should stored in Dimension tables either in Star Schema fashion or Snow Flake Schema fashion which is best suited to your reporting solution. Since attributes provide context for fact values, both fact columns and attribute ID columns are included in fact tables. Facts help to link indirectly related attributes using these attribute ID columns. The attribute ID columns included in a fact table represent the level at which the facts in that table are stored. So the level of a fact table in the Fact_Item_Day_Customer can be the attribute Id's which is at Day, Item & Customer Id level. For example, fact tables containing sales and inventory data look like the tables shown in the following diagram: Base fact columns ver...

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned. Case can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 , ReturnValue1 , Condition2 , ReturnValue2 ,..., DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV evaluates a single metric and returns different values according to the results. It can be used to perfo...

Microstrategy "Error type: Odbc error. Odbc operation attempted

"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

Optimizing queries in Microstrategy using VLDB properties

Optimizing queries in Microstrategy using VLDB properties #vldb #vldbproperties The table b elow summarizes the Query Optimizations VLDB properties. Additional details about each property, including examples where necessary, are provided in the sections following the table. Property Description Possible Values Default Value Additional Final Pass Option Determines whether the Engine calculates...

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...

Multi-Table Data Import(MTDI) from one or more supported data sources

Multi-Table Data Import(MTDI) from one or more supported data sources In MicroStrategy Analytics Enterprise Web 10 onewards, users can now simultaneously import two or more tables from one or more supported data sources, this feature is called Multi-Table Data Import (MTDI) which has been renamed as Super Cubes in MSTR 2019 (Does it sound like multisourcing for all the users without admin help?) Currently, all connectors in MicroStrategy Web 10 except " OLAP " and " Search Engine Indices " support Multi-Table Data Import. Users are able to add multiple tables/files when doing data import from single connector, as shown below: Users are also able to combine multiple tables/files from different sources and store them into one single Intelligent Cube, as shown below:

System Manager workflow to execute on a schedule

Creating a System Manager workflow to execute on a schedule System Manager workflow can execute on a schedule or after an event has been triggered. This can be accomplished by creating a simple batch file, and scheduling that batch file to execute with a third-party tool like Microsoft Task Scheduler. Note : To avoid user permission conflicts, the following steps must be performed with highest privileges. In the below example, the workflow makes the i-server restarts every day. 1. The user must first have a valid workflow. This particular workflow is a template that is delivered out-of-the-box with System Manager. 2. Save the workflow in .smw format. 3. In a text editor (such as Notepad), enter the command line statement that the task scheduler should execute. MASysMgr.exe -w C:\filename.smw” “UserName=User1 “Password=1234” 4. Save the file in .bat ...

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy FiscalWeek Returns the numeric position of a week within a fiscal year, for a given input date. This function is useful in financial reporting when the start of the fiscal year is different than the start of the calendar year. Syntax FiscalWeek< firstWeekDay , firstMonth >( Date / Time ) Where: • Date / Time is the input date or timestamp. • firstWeekDay (default value is 1) is a parameter that determines which day of the week is considered as the first day of the week. You can type an integer value from 1 to 7, with 1 representing Sunday, 2 representing Monday, and so on until 7 representing Saturday. • firstMonth (default value is 1) is a parameter that determines which month is considered as the start of the fiscal year. You can type an integer value from 1 to 12, with 1 representing January, 2 representing February, and so on until ...

Internationalization Design Technics

Microstrategy Internationalization Design Technics MicroStrategy supports data internationalization through two different techniques. You can either provide translated data through the use of extra tables and columns, or you can provide separate databases to store your translated data. These techniques are described below: You can support data internationalization in your database by using separate tables and columns to store your translated data. You can use various combinations of tables and columns to support and identify the translated data in your database. To support displaying the name of each month in multiple languages, you can include the translated names in a separate column, one for each required language, within the same table. Each column can use a suffix to identify that the column contains translated data for a certain language. The same LU_MONTH_OF_YEAR table with translated data for the Spanish and German langua...

Microstrategy Latest Video Tutorials including Transaction Services

Microstrategy Video Tutorials How to define VLDB properties? How to Configure Library Services: How to use Microstrategy for Tableau: Explore Sample Dossiers in Library How to add data to Dossiers How to explore and Search Library How to manage Dossier color palette How to create Combo Charts How to open a Dossier in New Window How to use sub-totals and sorting How to monitor with topology and platform analytics How to optimize performance with Cache MSTR on AWS: Cloud Console How to use bookmarks in Dossiers How to send Dossiers to user libraries How to create Histograms How to define relationship of multi table dataset How to create Line Charts How to add counter to your library: Microstrategy Dataset connection for Qlik Microstrategy Survey Monkey connector Transaction Services Tutorials Using Transaction ...

Microstrategy Analytics

Search This Blog