In. The arrows depict the override authority of the levels, with the report level having the greatest authority. They are exactly the same. Database Instance Level This is the most common place to set VLDB Properties. Upgrading Your Database Type Properties. Additional details about each property, including examples where necessary, are available by clicking on the links in the table. Additional details about each property, including examples where necessary, are provided in the sections following the table. In MicroStrategy Developer versions prior to 9. 3. This article addresses the change made to the Downward Outer Join setting. In MicroStrategy Developer, choose File > New > Report. (0 = unlimited number of rows; -1 = use value from higher level. 'Amazon Redshift offers a feature called WLM (WorkLoad Management). Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. When the VLDB property Intermediate Table Type is set to "True Temporary Table", each "SQL pass" is specified as a DECLARE GLOBAL TEMPORARY TABLE statement to define a. MicroStrategy Engine Components 27 MicroStrategy supported database platforms 276 MovingAverage function 255 Multipass SQL 37 N Nested Metrics 160 Non-Aggregatable metrics 142 O Oracle 292, 299, 304, 318, 327, 328, 329 Output level 193 P Partitioning 330 Permanent table 330 Permanent Tables 326 Pre/Post Statements 299 wildcards 301. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Accessing Database Instance VLDB Properties. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". For more information regarding post statements defined at the report level, refer to the following Technical Note:There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. DATA ANALYSIS 102. 5 : If the Use default inherited value check box is selected, clear it. VLDB properties allow you to customize the SQL that MicroStrategy generates. In the Metric Editor, on the Tools menu, point to Advanced Settings, and then select VLDB Properties. 4. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Both properties are located in the Query Optimizations folder in the VLDB property editor. Go to Database instances > SQL Data Warehouses. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. In MicroStrategy, there is a Very Large Data Base (VLDB) property, "Additional Final Pass Option," that configures whether or not the engine will optimize SQL into a single pass when possible. Group by alias. To set these properties, open the report in the Report Editor or Report Viewer. If the SQL of your Report has any Sub queries, You can use the “Use Temporary Table” option available in Query Optimization in VLDB Properties. For this reason, two additional options are provided:Export to PDF: export a report or document to a PDF document: EXPORTTOPDF:. The Null Checking for Analytical Engine VLDB property determines whether or not null values are interpreted as zeros when the Analytical Engine calculates data. The VLDB Properties Editor opens. . x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results. For information about accessing these properties, see. " Save and close. Choose one of the following: •. Temporary Table. Metrics using count or average, metrics with dynamic aggregation. This file can be modified to add additional VLDB properties to display in case non standard properties need to be changed in an environment. VLDB properties also help you configure and optimize your system. On MicroStrategy Web and Workstation, the same. The default syntax can be modified by using 'Column Pattern' VLDB property. Database instances for the project source are displayed. •. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. You can use this setting on the following levels: To edit the setting, you must have "Use VLDB property editor. Additional details about each property, including examples and a list of wild cards, are available by clicking on the links in the table. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. 15. Certain VLDB properties use different default settings depending on which data source you are using. Property. The final pass will perform two operations. Right-click on the project and select 'Configure project'. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. To help illustrate the functionality of the property, consider an unbalanced hierarchy with the levels Products, Department, Category, SubCategory, Item, and SubItem. MicroStrategy Library. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. Web Professional privileges. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Very Large Database (VLDB) properties are settings in charge of performing database specific optimizations (customizing Structured Query Language (SQL)). Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of levels in hierarchy * 10). The Grouping Properties dialog box opens. Among all , Report has highest priority and It always override the others . Any existing projects will retain the null checking behavior that was. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. x, "Use relational model" is selected by default. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. 3. 1 and 10. List Parent User Groups. " Uncheck the "Use default inherited value" checkbox. If necessary, you can ensure that a property is set to the default. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. Retrieve a list of user groups and the associated users in MicroStrategy Developer Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9. This section focuses on the VLDB properties that are set at the metric and report level. See the Advanced Reporting Guide. 0. . Scribd is the world's largest social reading and publishing site. Open MicroStrategy Developer. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. DATA ANALYSIS. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. Metric Qualification (MQ) Tables 3. Lookup Tables VLDB Settings provide minimal modifications to this order. You can specify another. Viewing and Changing VLDB Properties. Allow joins based on unrelated common. MicroStrategy implements a list of strategies through VLDB settings to generate temp table for the efficient execution of complex business queries. Retrieve a list of user groups and the associated users in MicroStrategy Developer Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9. Export a Report Services document to Excel with formatting using URL API in MSTR Web. Click on. Modify the VLDB property you want to change. What are VLDB properties in MicroStrategy? 39. For reports with several relationship filters, temporary table syntax may execute. Upgrading Your Database Type Properties. Group by position. VLDB properties allow MicroStrategy products to exploit the unique optimizations offered by different databases. The method used for multiple data source access is controlled by a project-level VLDB Property. Set the additional final pass property to force an additional pass of SQL. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. The recommended VLDB optimizations for Oracle 11g are listed below. The Dimensionality Model property is strictly for backward compatibility with MicroStrategy 6. Change the VLDB setting . This property is report-specific. Use this section to learn about the VLDB properties before modifying any default settings. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. Possible locations for VLDB optimizations in the query structure are. col2…) While the default values should result in the. XQuery Success Code is an advanced property that is hidden by default. If the size for a SQL pass. To create and review a detailed list of all the default VLDB settings for different DBMS types, see Default VLDB Settings for Specific Data Sources. KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. b. In our current design, report pre/post statement 5 is different from 1-4. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform14. Specifying the Display Mode and VLDB Properties. The properties are saved in different folders, as indicated in the previous list. 4. Metric-specific VLDB properties that can be set at the metric level include. To remove the COALESCE function from the SQL generated by the MicroStrategy SQL Engine, perform one of the following actions: At the project level, change the VLDB property 'Full Outer Join Support' to 'No support' from the Database Instance's VLDB properties under the 'Joins' group. Default VLDB properties are set according to the database type specified in the database instance. Click Save and Close to save your changes. x. Close suggestions Search Search. This VLDB setting can be changed at the Database instance, Report, and Metric levels. OR. Choose Tools > Show Advanced Settings option if it is not already selected. On the Advanced tab, select the Use parameterized queries check box. The VLDB Properties Editor opens. ; By default, the Bulk export database instance, which is the database instance for the database containing the report data, is defined as the data warehouse for the project. The Database Connections dialog box opens. It can be enabled on project level: Open MicroStrategy Developer. For a data source, right-click it and choose Edit. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3. 3. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. The VLDB Properties Editor opens. To access the VLDB properties editor at the project level in the MicroStrategy Cloud Environment, please use either a Desktop Designer or Architect user account to connect to MicroStrategy Developer. " Save and close. MicroStrategy’s VLDB driver for Azure SQL Data Warehouse is designed to use SQL DW-specific features when they lead to improved performance or analytical functionality. The fact columns can also be included in the primary index, using the Allow index on metric VLDB property. Integer Constant in Metric; Metric Join Type; Null Check; Zero CheckThis manual runs through VLDB Properties, Internationalization, User Privileges, and Other Supplemental Information for Administrators. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. You must have the " Use VLDB property editor " privilege to make changes to the setting. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform Products; MicroStrategy ONE; AI & Augmented; Dossier; Library; Workstation; HyperIntelligence; Multi-Cloud; Embedded Analytics; Innovations; Futures. KB19860: What is the ‘Attribute Selection Option for Intermediate Pass’ VLDB property in MicroStrategy Developer 10. Click Save and Close to save your changes. Here, we will use MicroStrategy Tutorial objects. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. The following settings are advanced properties which are. Open navigation menu. MicroStrategy can support multiple (more than 5) pre-statements to put in a report. 2. Non-aggregatable metrics are defined in MicroStrategy using the metric dimensionality Grouping = Beginning or Ending (fact. The VLDB property's behavior will be demonstrated using the following attribute and report. You can determine the default options for each VLDB property for a database by performing the steps below. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. Project-Level VLDB settings: Click to configure the analytical engine settings. A given VLDB setting can support or. This setting is useful if you have only a few attributes that require different join types. Open the report template in the Template Editor. From the Tools menu, select Grouping. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. This VLDB setting is located in the 'Indexing' folder and has the following options:In MicroStrategy Web, open the document in Design or Editable Mode. See KB484738 for more information. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. VLDB Editor for Select Statement Post String (ORDER BY PO_APPROVED_DATE_DESC) Drill from Summary Report to Report Template which includes SQL Hint (TOP 25) and new Select Statement Post String SQL that is Generated Keep in mind that these VLDB properties are introducing custom SQL to filter out the data with out the MicroStrategy Engines knowledge. This set of unrelated VLDB properties includes the Metric Join Type setting. The Project Configuration Editor opens. Right-click your project and select Project Configuration. Choose Data > Configure Bulk Export. Sometimes pre-statement VLDB Properties are used to set database priority. 1 and 10. ")This is a known issue prior to MicroStrategy SQL Engine 9. Open the report template in the Template Editor. a. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. The setting is applied. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. The Character Column Option and National Character Column Option VLDB properties can also support the scenario where two character sets are used, and Unicode is not one of these character sets. x where report SQL statement containing semi-colon (;) in the Report Pre Statement 5 VLDB properties will cause report to fail in MicroStrategy 10. Click the "VLDB Properties. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Use the SQL Date Format VLDB property to format the date string to match the attribute's description (MEMBER_NAME property in the cube). wanttobuildandresellMicroStrategy-basedproductsorapplicationssuitedto particularindustries. 10 Snowflake Derived Tables require non-standard Outer Join VLDB property settings. 4. You can connect to multiple projects on. In MicroStrategy Developer, open a report in the Report Editor. •. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. As shown in the example above, all data for cost is aggregated together and shown for every row of a category. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. mstrc) Open Workstation. Click Properties. The Database Instances Editor opens. Web Analyst privileges. This Knowledge Base article describes how using Snowflake data base outer joins are automatically set as off/ (nosupport) SYMPTOM. The two possible values are as. Deliveries privileges. To use automatic attribute role recognition, you must select the Engine Attribute Role Options, found in the database instance-level VLDB Properties under Query Optimization. The root cause is unknown, however it is related to an issue with the upgrade where the property set object that contains the two properties is not properly updated. Dependent Object Options: Enable Find and Replace object dependencies: If the checkbox is selected, a user is allowed to find all dependent objects and replace them. Changes made to this VLDB setting can cause differences to appear in your data output. This guide discussesBy selecting this option, the Join Type VLDB property is assumed to be Join 92 and any other setting in Join Type is ignored. This article describes the best practices to be taken when connecting an instance of Azure Synapse Analytics in MicroStrategy. To create and review a detailed list of all the default VLDB settings for different DBMS types, see Default VLDB Settings for Specific Data Sources. Access the VLDB Properties Editor. Zillow has 471 homes for sale in Victoria BC. If this VLDB property is not displayed, you must upgrade the project metadata. Cross joins are seen in metrics when joining across unrelated attributes inside of data blending. Clear the Use default inherited value check box. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. x order - Calculate. The "Evaluation Ordering" VLDB setting has two possible values, "6. The Database instances - SQL Data warehouses pane displays. col2…) While the default values should result in the. Clicking in Preserve all pass the final elements option. . Diagnosis. Visit REALTOR. Rank) calculated in Analytical Engine" found under the 'Metrics' folder in the list of VLDB properties. See Details for All VLDB Properties for more information. Choose the database instance and then open VLDB Properties. On the Advanced tab, select the Use parameterized queries check box. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. This setting is called Join Across Datasets. The “#n” code in Apply function syntax serves as placeholders for the MicroStrategy objects being passed to your database. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. Group by column. 8 From the File menu, click Save As. VLDB properties allow you to customize the SQL that MicroStrategy generates. See Viewing and Changing Advanced VLDB Properties for more information on how to display this property. Single SQL pass time-out in seconds. Select either Disable or Enable depending on whether you want to disable or enable. ACTIONWith MicroStrategy, a VLDB property exists for reports executing against MDX data sources. MicroStrategy ONE introduces new features that provide better performance and scalability to enhance the overall user experience. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategyMicroStrategyEnginesAndSQL 11 2 1. There are number of them. x order - Calculate. It is strongly encouraged that you post your questions on the community forum for any community. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. Only project configured with those setting is applicable for the case in this article. 1 and 10. In MicroStrategy it is possible to generate outer joins between metrics at different levels, but there was the possibility of report results that could vary in ways outside the user's control if a straight outer join was performed. Open the database instance for the project. VLDB_PROPERTY_NAME: The. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. Follow the steps below to change the property. In MicroStrategy SQL Generation Engine, the VLDB property "Preserve all final pass result elements" is designed for the case in which data elements exist in a fact table that are missing from an attribute's lookup table. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. Check the report SQL, and observe that permanent tables are still used as intermediate tables. The Display mode setting determines how the drilled-to report is displayed, as one of the following options: Default: Uses the original report's display setting. 3) Explain how intelligent cubes are different from ordinary cubes?. Certain VLDB properties use different default settings depending on which data source you are using. Property owners benefit from a fair number of nearby clothing stores. The reports created from an intelligent cube do not have this VLDB property used in normal reports. To specify this setting, edit the VLDB properties for the database instance or for a report, expand Governing settings, then select the SQL Time Out (Per Pass) option. ; Click the General tab. To overcome these challenges, we first analyze a real-world query trace from Snowflake and compare its properties to that of TPC-H and TPC-DS. VLDB properties also help you configure and optimize your system. The privileges are grouped by privilege type: Web Reporter privileges. Database Instance Level; Joins -> Cartesian Join Warning), either one or both of the two new VLDB properties, "Document Grids from Multiple Datasets" and "Remove Missing Units in Documents", are not shown: CAUSE. This information is available for each property in the VLDB Properties dialog box at each level. ca. A simple metric sum (Revenue) will go to different aggregate tables depending on the attributes on the template. This section tells you how to do the following:VLDB properties let you to customize the SQL that MicroStrategy generates when a report is executed, and determine how data is processed by the Analytical Engine. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. 1 includes a new VLDB property, Custom Group Display for Joint Elements'. Number of Views 948. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to fa. Global Optimization is a SQL Generation Engine feature that analyzes similarities and relationships between SQL passes, to reduce the number of passes where possible and improve report. ; By default, the Bulk export database instance, which is the database instance for the database containing the report data, is defined as the data warehouse for the project. Beginning with MicroStrategy 8. Right click on your project and click “Project Configuration…”. Choose Tools > Show Advanced Settings option if it is not already selected. However, you set. Report designers can then view the messages immediately without accessing the Intelligence Server machine. Export to PDF filter summaries include the full attribute and metric names. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. 1. One possible cause is some registry keys have some inconsistency. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X" as shown below: However, the images in the report display properly when the report is executed in. 4. 1, this can be done at the report level by following the steps in technical note 10073. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. A given VLDB setting can support or optimize one system setup, but the same setting can cause performance issues or errors for other systems. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. A given VLDB setting can support or. This VLDB property is useful only for MDX cube reports that access an Oracle Hyperion Essbase MDX cube source. Click VLDB Properties. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Dependent Object Options: Enable Find and Replace object dependencies: If the checkbox is selected, a user is allowed to find all dependent objects and replace them. SQL Global Optimization This setting can reduce the number of SQL passes generated by MicroStrategy. Other VLDB settings that affect query generation The MicroStrategy platform provides VLDB settings for all supported RDBMS platforms to generate optimized SQL that takes advantage of database-specific functionality. <Setting> If that level is also set to the default or if the VLDB property is not set at the project level, the setting at the database instance is used. Modify the VLDB property you want to change. Changing an option in one of the editors automatically reads the changes and is reflected in the other editor as well. The Intermediate Table Type property specifies what kinds of intermediate tables are used to execute the report. The 'Where clause driving table' Very Large Database (VLDB) property indicates to the MicroStrategy Engine which table to use when a filter needs to be applied. Check the report SQL again, observe that "with" clause (aka common table expression) is applied. For more details, go to Start . Since full outer joins can require a lot of database and Intelligence Server resources, and full outer joins are not supported for all databases, it. NULL values can be treated as zeroes (0) for computational purposes by enabling suitable settings in the Very Large Database (VLDB) properties at the project, report, and metric levels. Select the radio button labeled "Outer Join. MicroStrategy periodically updates the default settings as database vendors add new. To access the setting, in MicroStrategy Developer right-click on the project and select Project Configuration…Then, In the Project Configuration dialog box, choose Project Definition >. Most major databases have allowed the creation of special tables that have characteristics that separate them from 'normal' or 'permanent' tables in the. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. x and 10. The properties are saved in different folders, as indicated in the previous list. This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategy. Possible Values Default Values; Metrics Join Across Datasets: Determines how values for metrics are calculated when unrelated attributes, from different datasets of a dossier or document, are included with metrics. 9 Name the report Indexing Analysis. For examples and details to enable these properties, see SQL Generation and Data Processing: VLDB Properties. The four attribute join types available in the Report Data Options dialog box are the same as those in the VLDB Properties dialog box. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. Click VLDB Properties. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. 6 :Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. The MicroStrategy platform provides VLDB settings for all supported RDBMS platforms to generate optimized SQL that takes advantage of database-specific functionality. VLDB. Enable. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. Be careful though, because these settings are applied set as the defaults for. Doing so, we. Any projects that existed prior to upgrading metadata to MicroStrategy 2020 retain their original VLDB property settings. Report Caching Options, available to users with. The following list summarizes the metric-specific VLDB properties that can be set at the metric level. In the Project Configuration Editor, expand Project definition, and select Advanced. This section tells you how to do the following:When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Expand the 'Governing' folder and select 'SQL Time Out (Per Pass). You can determine the default options for each VLDB property for a database by performing the steps below. The Year - Define a new member attribute. To be effective. The recommended VLDB optimizations for Teradata 12 (and higher) are listed below. In MicroStrategy Developer, right-click the project to update, and select Project Configuration. Dimensionality Model is an advanced property that is hidden by default. This VLDB property has the following options: Disable parallel query execution (default) : All queries for MicroStrategy reports and Intelligent Cubes are processed sequentially. 2.