Skip to main content

Optimizing queries in Microstrategy using VLDB properties

Optimizing queries in  Microstrategy using VLDB properties

#vldb #vldbproperties

The table below 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 an aggregation function and a join in a single pass or in separate passes in the SQL.
• (default) Final pass CAN do aggregation and join lookup tables in one pass
• One additional final pass only to join lookup tables
Final pass CAN do aggregation and join lookup tables in one pass
Apply Filter Options
Indicates during which pass the report filter is applied.
• Apply filter only to passes touching warehouse tables
• Apply filter to passes touching warehouse tables and last join pass, if it does a downward join from the temp table level to the template level
• Apply filter to passes touching warehouse tables and last join pass
Apply filter only to passes touching warehouse tables
Attribute Element Number Count Method
Controls how the total number of rows are calculated for incremental fetch.
• Use Count(Attribute@ID) to calculate total element number (uses count distinct if necessary)
• Use ODBC cursor to calculate total element number
Use Count(Attribute@ID) to calculate total element number (uses count distinct if necessary)
For Tandem databases, the default is Use ODBC Cursor.
Count Distinct with Partitions
Determines how distinct counts of values are retrieved from partitioned tables.
• Do not select distinct elements for each partition
• Select distinct elements for each partition
Do not select distinct elements for each partition
Custom Group Banding Count Method
Helps optimize custom group banding when using the Count Banding method. You can choose to use the standard method that uses the Analytical Engine or database-specific syntax, or you can choose to use case statements or temp tables.
• Treat banding as normal calculation
• Use standard case statement syntax
• Insert band range to database and join with metric value
Treat banding as normal calculation
Custom Group Banding Points Method
Helps optimize custom group banding when using the Points Banding method. You can choose to use the standard method that uses the Analytical Engine or database-specific syntax, or you can choose to use case statements or temp tables.
• Treat banding as normal calculation
• Use standard case statement syntax
• Insert band range to database and join with metric value
Treat banding as normal calculation
Custom Group Banding Size Method
Helps optimize custom group banding when using the Size Banding method. You can choose to use the standard method that uses the Analytical Engine or database-specific syntax, or you can choose to use case statements or temp tables.
• Treat banding as normal calculation
• Use standard case statement syntax
• Insert band range to database and join with metric value
Treat banding as normal calculation
Data population for Intelligent Cubes
Defines if and how Intelligent Cube data is normalized to save memory resources.
• Do not normalize Intelligent Cube data
• Normalize Intelligent Cube data in Intelligence Server
• Normalize Intelligent Cube data in database using Intermediate Table Type
• Normalize Intelligent Cube data in database using Fallback Type
• Normalize Intelligent Cube data basing on dimensions with attribute lookup filtering
• Normalize Intelligent Cube data basing on dimensions with no attribute lookup filtering
Normalize Intelligent Cube data in Intelligence Server
Data population for reports
Defines if and how report data is normalized to save memory resources.
• Do not normalize report data
• Normalize report data in Intelligence Server
• Normalize report data in database using Intermediate Table Type
• Normalize report data in database using Fallback Table Type
• Normalize report data basing on dimensions with attribute lookup filtering
Do not normalize report data
Default Sort Behavior for Attribute Elements in Reports
Determines whether the sort order of attribute elements on reports considers special sort order formatting defined for attributes.
• Sort attribute elements based on the attribute ID form for each attribute
• Sort attribute elements based on the defined 'Report Sort' setting of all attribute forms for each attribute
Sort attribute elements based on the attribute ID form for each attribute
Dimensionality Model
Determines level (dimension) replacement for non parent-child related attributes in the same hierarchy.
• Use relational model
• Use dimensional model
Use relational model
Engine Attribute Role Options
Enable or disable the Analytical Engine's ability to treat attributes defined on the same column with the same expression as attribute roles.
• Enable Engine Attribute Role feature
• Disable Engine Attribute Role feature
Disable Engine Attribute Role feature
Filter tree optimization for metric qualifications
Determines if metric qualifications that are included in separate passes of SQL are included in a single pass of SQL when possible.
• Enable Filter tree optimization for metric qualifications
• Disable Filter tree optimization for metric qualifications
Enable Filter tree optimization for metric qualifications
Incremental Data Transfer
Determines whether data that is transferred between Intelligence Server and a database is performed using a single transfer of data or multiple, incremental transfers of data
• Enable Incremental Data Transfer
• Disable Incremental Data Transfer
Disable Incremental Data Transfer
Maximum Parallel Queries Per Report
Determines how many queries can be executed in parallel as part of parallel query execution support
User-defined
2
MD Partition Prequery Option
Allows you to choose how to handle prequerying the metadata partition.
• Use count(*) in prequery
• Use constant in prequery
Use count(*) in prequery
Multiple data source support
Defines which technique to use to support multiple data sources in a project.
• Use MultiSource Option to access multiple data sources
• Use database gateway support to access multiple data sources
Use MultiSource Option to access multiple data source
OLAP function support
Defines whether OLAP functions support backwards compatibility or reflect enhancements to OLAP function logic.
• Preserve backwards compatibility with 8.1.x and earlier
• Recommended with 9.0 and later
Preserve backwards compatibility with 8.1.x and earlier
Parallel Query Execution
Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes.
• Disable parallel query execution
• Enable parallel query execution for multiple data source reports only
• Enable parallel query execution for all reports that support it
Disable parallel query execution
Parallel Query Execution Improvement Estimate in SQL View
Determines whether reports and Intelligent Cubes include an estimate in the percent of processing time that would be saved if parallel Query execution was used to run multiple queries in parallel.
• Disable parallel query execution improvement estimate in SQL view
• Enable parallel query execution improvement estimate in SQL view
Disable parallel query execution improvement estimate in SQL view
Rank Method if DB Ranking Not Used
Determines how calculation ranking is performed.
• Use ODBC ranking (MSTR 6 method)
• Analytical engine performs rank
Use ODBC ranking (MSTR 6 method).
Remove Aggregation Method
Determines whether to keep or remove aggregations in SQL queries executed from MicroStrategy.
• Remove aggregation according to key of FROM clause
• Remove aggregation according to key of fact tables (old behavior)
Remove aggregation according to key of FROM clause
Remove Group By Option
Determines whether Group By and aggregations are used for attributes with the same primary key.
• Remove aggregation and Group By when Select level is identical to From level
• Remove aggregation and Group By when Select level contains all attribute(s) in From level
Remove aggregation and Group By when Select level is identical to From level
Remove Repeated Tables For Outer Joins
Determines whether an optimization for outer join processing is enabled or disabled.
• Disable optimization to remove repeated tables in full outer join and left outer join passes
• Enable optimization to remove repeated tables in full outer join and left outer join passes
Enable optimization to remove repeated tables in full outer join and left outer join passes
Set Operator Optimization
Allows you to use set operators in sub queries to combine multiple filter qualifications. Set operators are only supported by certain database platforms and with certain sub query types.
• Disable Set Operator Optimization
• Enable Set Operator Optimization (if supported by database and [Sub Query Type])
Disable Set Operator Optimization
SQL Global Optimization
Determines the level by which SQL queries in reports are optimized.
• Level 0: No optimization
• Level 1: Remove Unused and Duplicate Passes
• Level 2: Level 1 + Merge Passes with Different SELECT
• Level 3: Level 2 + Merge Passes, which only hit DB Tables, with different WHERE
• Level 4: Level 2 + Merge All Passes with Different WHERE
Level 4: Level 2 + Merge All Passes with Different WHERE
Sub Query Type
Allows you to determine the type of subquery used in engine-generated SQL.
• WHERE EXISTS (SELECT * ...)
• WHERE EXISTS (SELECT col1, col2...)
• WHERE COL1 IN (SELECT s1.COL1...) falling back to EXISTS (SELECT * ...) for multiple columns IN
• WHERE (COL1, COL2...) IN (SELECT s1.COL1, s1.COL2...)
• Use Temporary Table, falling back to EXISTS (SELECT *...) for correlated subquery
• WHERE COL1 IN (SELECT s1.COL1...) falling back to EXISTS (SELECT col1, col2 ...) for multiple columns IN
• Use Temporary Table, falling back to IN (SELECT COL) for correlated subquery
Use Temporary Table, falling back to EXISTS (SELECT *...) for correlated subquery
Transformation Formula Optimization
Defines whether to attempt to improve performance of reports that use expression-based transformations.
• Always join with transformation table to perform transformation
• Use transformation formula instead of join with transformation table when possible
Use transformation formula instead of join with transformation table when possible
Unrelated Filter Options
Determines whether the Analytical Engine should keep or remove the unrelated filter.
• Remove unrelated filter
• Keep unrelated filter
• Keep unrelated filter and put condition from unrelated attributes in one subquery group
Remove unrelated filter
Unrelated Filter Options for Nested Metrics
Determines whether the Analytical Engine should keep or remove the unrelated filters when using nested metrics.
• Use the 8.1.x behavior:
• Use the 9.0.x behavior:
Use the 8.1.x behavior
WHERE Clause Driving Table
Determines the table used for qualifications in the WHERE clause.
• Use lookup table
• Use fact table
Use fact table







Labels:

Comments

Post a Comment

Popular posts from this blog

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...
2 comments
Read more

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...
3 comments
Read more

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...
4 comments
Read more

Custom Tooltips in Microstrategy developer and Web

Custom Tooltips in Microstrategy developer and Web The following table describes the macros you can use to customize graph tooltips in both MicroStrategy Developer and MicroStrategy Web: Macro Information Displayed {&TOOLTIP} All relevant labels and values associated with a graph item. {&GROUPLABEL} Name of the graph item's category. This value is often the graph item's attribute element information, as attributes are commonly used as the categories of graph reports. {&SERIESLABEL} Name of the graph item’s series. This value is often the graph item's metric name information, as metrics are commonly used as the series of graph reports. {&VALUE} The value of a given data point. {&XVALUE} The X-value of a data point. Only applicable to Bubble charts and Scatter plots. {&YVALUE} The Y-value of a data point. Only applicable to Bubble charts and Scatter plots. {&ZVALUE} The Z-value of a data point. Only applicable to Bubble charts and Scatter plots. {...
2 comments
Read more

Transaction Services - Configure Transactions

Configure Transactions in MSTR Web Transaction Services-enabled document displayed on an iPhone, iPad, or Android device can allow users to insert/update/delete data in to the database, using the options in the Configure Transactions Editor. To do so, you must link a Transaction Services report to a grid or to text fields in a panel stack. If the document is being displayed on an iOS device, you can link the report to the cells of a transaction table. Data from the input objects defined in the Transaction Services report is displayed in the grid, text fields, or cells for users to edit. Prerequisites:        Ø   You must have the Web Configure Transaction privilege assigned by MSTR user admin. Ø   Create the Transaction Services report (usually a grid report) you want to link to the grid, text fields, or transaction table cells. Make sure that the Transaction Services report must contain the input object for each value you w...
2 comments
Read more

Data Mart Reports in Microstrategy

Creating Data Mart Reports in Microstrategy   When there is requirement to store all the report results to a database table you can use the interesting feature in Microstratgey called Data Mart Reports. To create a data mart table, you first create a data mart report that defines the columns of the data mart table. You then create the data mart table and populate it with data. The steps below walk you through the process of creating a data mart report and then executing the report to create a data mart table. The steps also include an example for most steps, based on Tutorial sample data in the MicroStrategy Tutorial project.                Follow the simple steps below to create a datamart report: 1 In MicroStrategy Developer, create a new report or select an existing report to use as the data mart table. The report should contain the attributes...
1 comment
Read more

Bursting file subscriptions Microstartegy

Bursting file subscriptions: Delivering  parts of reports across multiple files: Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis). Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region. As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Ele...
1 comment
Read more

Create an alert-based subscription in MicroStrategy Distribution Services

Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief  steps bel...
2 comments
Read more

Types of filters in Microstrategy

Types of filters in Microstrategy Below are the types of filters: 1. Attribute qualification filter These types of qualifications restrict data related to attributes on the report. a) Attribute form qualification Filters data related to a business attribute’s form(s), such as ID or description. •  For example, the attribute Customer has the forms ID, First Name, Last Name, Address, and Birth Date. An attribute form qualification might filter on the form Last Name, the operator Begins With, and the letter H. The results show a list of customers whose last names start with the letter H. b) Attribute element list qualification Filters data related to a business attribute’s elements, such as New York, Washington, and San Francisco, which are elements of the attribute City. • For example, the attribute Customer has the elements John Smith, Jane Doe, William Hill, and so on. An attribute element list qualification can filter data to display only those customer...
5 comments
Read more

Microstrategy Document Autotext macros:

Autotext  code/macros in  Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add  document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard:  AUTOTEXT DESCRIPTION   {&PAGE}  Display the current page.  {&NPAGES}  Display the total number of pages.  {&DATETIME}  Display the current date and time.  {&USER}  Display the user name that is executing the Report Services Document.  {&DOCUMENT}  Display the document name.  {&DOCUMENTID}  Display the document ID.  {&DESCRIPTION}  Display the document description.  {&PROJECT}  Display the project name.  {&EXECUTIONTIME}  Dis...
2 comments
Read more