Accessing Database Instance VLDB Properties. Under Query Optimizations, select SQL Global Optimization. By default, all properties are governed by the one at the top level. Both properties are located in the Query Optimizations folder in the VLDB property editor. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. DeanElectronHummingbird14. The privileges are grouped by privilege type: Web Reporter privileges. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. 15. MicroStrategy Office privileges. 1 and 10. However, platform administrators can toggle this functionality if needed: In MicroStrategy Developer, platform administrator can select/deselect the Use parameterized queries checkbox under the Advanced tab of the Database Connections dialog. KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. 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 setting is used as an optimization for some databases which perform better when columns coming. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. Recommendations. ) From the Tools menu, select Show Advanced Settings. Pre- and Post-statements defined in the VLDB Properties of a project's primary warehouse database instance also apply to attribute element browsing requests, which are issued when browsing attribute elements in the data explorer in MicroStrategy Developer, or when a prompt must display a list of attribute elements. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. The MicroStrategy Knowledge Base document KB6100-071-0031 explains how to change default Very Large Database (VLDB) properties for all database instances on the same MicroStrategy Intelligence Server. 6 :Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. Expand the 'Governing' folder and select 'SQL Time Out (Per Pass). MicroStrategy Transaction Services and XQuery allow you to access. In the Metric Editor, on the Tools menu, point to Advanced Settings, and then select VLDB Properties. 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. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. These properties apply only to MDX cube reports using data from an MDX cube. The index for referencing these objects begins with 0 and increases by for each successive object passed. See the warning above if you are unsure about whether to set properties to the default. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. When creating attribute relationship filters, the default Very Large Database (VLDB) property for sub query types causes EXISTS statements to appear in the sub queries. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. VLDB properties can provide support for unique configurations. This. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. As shown in the example above, all data for cost is aggregated together and shown for every row of a category. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. The reports created from an intelligent cube do not have this VLDB property used in normal reports. From the Data menu, select VLDB Properties. 4. Property. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. . At the DBMS and database instance levels, it is set in the VLDB Properties Editor. As mentioned, these steps will need to be done for each report that sorting in this way is desired. Under VLDB Settings, navigate to the desired VLDB option. Use this section to learn about the VLDB properties before modifying any default settings. Select either Disable or Enable depending on whether you want to disable or enable. 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. XQuery Success Code is an advanced property that is hidden by default. Lets you identify attributes that include empty elements, which can then be ignored when. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. Non-aggregatable metrics are defined in MicroStrategy using the metric dimensionality Grouping = Beginning or Ending (fact. DATA ANALYSIS 102. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. See the Advanced Reporting Guide. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. The Year - Define a new member attribute. Right click on your project and click “Project Configuration…”. 199 Exercise 7. At the metric level, it can be set in either the VLDB Properties Editor or from the Metric Editor's Tools menu, and choosing Metric Join Type. This VLDB settings influence the table creation type in the SQL passed to the Teradata database when Intermediate Table Type is set to True Temporary. You can configure properties. This technical article explains expected new behavior in MicroStrategy 10. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. MicroStrategy implements a list of strategies through VLDB settings to generate temp table for the efficient execution of complex business queries. Base Table Join for Template. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. This allows SQL to be run after the report execution, and is not tied to the subscription. "The table below summarizes the Joins VLDB properties. 4. Click the "VLDB Properties. The following settings are advanced properties which are. Sometimes pre-statement VLDB Properties are used to set database priority. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. ; 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 Data population for Intelligent Cubes VLDB property allows you to define if and how Intelligent Cube data is normalized to save memory resources. For an Intelligent cube or incremental refresh report, right-click it and choose Edit. Scribd is the world's largest social reading and publishing site. If the size for a SQL pass. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. From the Tools menu, select Create VLDB Settings Report. If you perform this procedure, any changes you may have made to any or all VLDB properties displayed in the chosen view of the VLDB Properties Editor will be. To address this issue, a VLDB property called "Downward Outer Join" should be used. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Pages 100+ Identified Q&As 2. Published: 4월 6, 2017. It is strongly encouraged that you post your questions on the community forum for any community based. However, there is no governing for in-memory executions, including data blending which creates unnecessary risk to the stability and performance of the. 3. The following. Web Analyst privileges. 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. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the business reports. STEPS TO REPRODUCE: In Web, create a report with the attributes Customer Region, Category,. The VLDB Properties (Report) dialog box opens. Loading × Sorry to interruptPlaces to Set VLDB Properties. You can specify another. Group by alias. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. In MicroStrategy 7. en Change Language. The Transformation Editor opens with the Select a Member Attribute dialog box displayed. 1 and 10. KB19860: What is the ‘Attribute Selection Option for Intermediate Pass’ VLDB property in MicroStrategy Developer 10. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. If an environment does not already exist, an environment will need to be created first. The table b elow summarizes the MultiDimensional Expression (MDX) related VLDB properties. The arrows depict the override authority of the levels, with the report level having the greatest authority. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. Close suggestions Search Search. Clear the Use default inherited value check box. It is very. Viewing VLDB properties. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Doc Preview. Accessing Report VLDB Properties. However, you want to show all the store. The “#n” code in Apply function syntax serves as placeholders for the MicroStrategy objects being passed to your database. ' If the check box 'Use default inherited value' is checked, then check this setting at the Database Instance (project) level; otherwise increase the value to a number (this is in seconds and 0 means no time out) that suits the report. One way to implement multi-pass SQL is to execute each pass (each query block) in a separate table. To change the VLDB properties at any of the three levels, execute the following: Database Instance Level: Right-click on the Project name > Project Configuration. The option "SQL Global Optimization" under Query Optimizations is not available when a report VLDB properties need to be changed. Upgrading Your Database Type Properties. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. 4. 4. KB40199: "The tokens 'NTLINK' and 'IMPORTWINUSER' should not be used. 3. Select a SQL Global Optimization level. 3. For use cases, examples, sample code, and other information on every VLDB property. Database Instance > VLDB Properties Report Level: Data > VLDB. Click the Load button. In MicroStrategy Developer, right-click the project to update, and select Project Configuration. . In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. Since MicroStrategy Analytical Engine 9. The Parallel Query Execution is an advanced property which determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. 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. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy In MicroStrategy SQL Generation Engine, a VLDB (Very Large Data Base) property "Set Operator Optimization" provides. The following list offers a detailed trace of each property available in Developer and its new place in MicroStrategy’s modern tools, such as Workstation. This section focuses on the VLDB properties that are set at the metric and report level. What are VLDB properties in MicroStrategy? 39. To View and Change VLDB Properties Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. Execute the report and view the SQL:September 06, 2018. Right-click on the report and click on the 'Edit' menu. VLDB properties are available at multiple levels, so that SQL generated for one report can be manipulated separately from the SQL generated for another, similar report. !o inserts the report name (can be used in all Pre/Post statements). For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. You can return all VLDB properties (those displayed in your chosen instance of the VLDB Properties Editor) to the default settings recommended for your database platform by MicroStrategy. In MicroStrategy Developer 9. Select either Disable or Enable depending on whether you want to disable or enable. Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. In the Source area, select a database instance for the database to access using Freeform SQL. Database Instance Level This is the most common place to set VLDB Properties. Common privileges. Group by position. 2. 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. Maximum SQL Size (Database Instance) You can limit the size (in bytes) of the SQL statement per pass before it is submitted to the data warehouse. This VLDB setting is located in the 'Indexing' folder and has the following options:MicroStrategy constantly optimizes the queries and sets new defaults for the VLDB properties so customers can take advantage of the best performance possible. To change the parameter PARAM_QUERY_ROWSET_SIZE, add the lines below (adjusting for a number of rows to insert at a time) to ODBCConfig. There are number of them. Open the report template in the Template Editor. When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. The "Evaluation Ordering" VLDB setting has two possible values, "6. This article explains the behavior of the commit level VLDB propertyThe MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. (For information on object levels, see Order of Precedence . Certain attribute-to-attribute comparisons may require subqueries. 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. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. Edit the report. After changing the options, check the query that will be created in SQL preview. Expand the Database instances folder. Any projects that existed prior to upgrading metadata to MicroStrategy 2020 retain their original VLDB property settings. Using the Select Statement Post String VLDB property, MicroStrategy can support this. for more information on this setting. MicroStrategy online help and PDF manuals (available both online and in printed format) use standards to help you identify. Possible locations for VLDB optimizations in the query structure are listed below. This article describes how to use wildcards to display temporary table names in pre/post statements. KB441418: Supplemental reference for installing Hotfix on MicroStrategy version 10. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the (missing or bad snippet) for steps to set this VLDB property. For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. List Nondefault Report VLDB Properties. Right-click a database instance and select Edit. To help illustrate the functionality of the property, consider an unbalanced hierarchy with the levels Products, Department, Category, SubCategory, Item, and SubItem. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Disallow joins based on unrelated common attributes. PDS file. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. Enable. How to change the syntax is described in detail by using examples. - On MicroStrategy Developer main toolbar, cick on ToolsProject Documentation - Follow the wizard selecting: (1) Application Objects (2) Advanced DefinitionIt is found in the Analytical Engine folder of the VLDB Properties (Metric) dialog box, pictured below. 0. . The Project Configuration Editor opens. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy In MicroStrategy SQL Generation Engine, a VLDB (Very Large Data Base) property "Set Operator Optimization" provides the option to use database-side set operators to combine intermediate results sets representing set qualifications in filters. Open a grid report. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. wanttobuildandresellMicroStrategy-basedproductsorapplicationssuitedto particularindustries. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. For a project, right-click it and choose Advanced Properties. You can configure this setting. On the Advanced tab, select the Use parameterized queries check box. The Table Creation Type property tells the SQL Engine whether to create a table implicitly or explicitly. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Choose Tools > Show Advanced Settings option if it is not already selected. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. Both properties are located in the Query Optimizations folder in the VLDB property editor. Fact Tables 2. ; Click the General tab. The solution is to backup old registry keys and re-generate default ones. By default, they are defined by MicroStrategy, optimized for the database and its version. 3. On the Freeform Sources tab, select Create Freeform SQL report. Clear the Use default inherited value check box. The VLDB properties at the different levels work together to affect report results. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. A possible business case that could be solved by this approach: A large fact table that summary reports are sourcing, from which it is necessary to drill down through a report (or report template) to row level data. In the confirmation window that appears, click Yes. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. 3) Explain how intelligent cubes are different from ordinary cubes?. These settings affect how MicroStrategy Intelligence Server manages joins, metric. All entries follow a set format as noted below. These settings are available only if the drill path destination is a template. Metrics using count or average, metrics with dynamic aggregation. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. It is strongly encouraged that you post your questions on the community forum for any community. This VLDB property determines how MicroStrategy joins tables with common columns. In MicroStrategy Developer, open a report in the Report Editor. 1 and 10. The MicroStrategy Tutorial project uses aggregate tables by default. Modify the VLDB property you want to change. They can be set at different levels throughout a project to establish a specific behavior regarding the object type. 1, VLDB properties may be enabled in Intelligent Cube reports and user reports to include Dynamic Sourcing diagnostic messages in SQL View. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. In the lower-right. These values are set by default when the "Teradata 12" database object is used (set at Configuration Managers > Database Instances > Database Instance. In Developer: Go to Tools > Developer Preferences. Modify the VLDB property you want to change. In MicroStrategy 10. '. Certain VLDB properties use different default settings depending on which data source you are using. The Use default inherited value option indicates the level that is active, while the SQL preview box. ; 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. Select Teradata V2R4 and move it to the right using the > button. 4. x. It is recommended to always stay on the latest MicroStrategy release so you can always have the best Snowflake experience out of the box. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. This setting affects all the metrics in this project, unless it is overridden at a lower level. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. The upgrade database type window appears. (0 = time limit not enforced by this governing setting)The MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. 1) From the Data menu, access the VLDB Properties option. Export to PDF filter summaries include the full attribute and metric names. When they do appear, report designers have some degree of control over the subquery syntax using the Very Large Data Base. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Rank) calculated in Analytical Engine" found under the 'Metrics' folder in the list of VLDB properties. It sets the general standards. In MicroStrategy Developer 9. Restart the Intelligence server to apply the changes. VLDB. 4. Single SQL pass time-out in seconds. At the report level, change the. Refer to the MicroStrategy System Administration Guide for a detailed description of these properties. Description. 0. ; Click the General tab. Within here there are. There are a number of them. You can determine the default options for each VLDB property for a database by performing the steps below. MicroStrategy 9. 4. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. The fact columns can also be included in the primary index, using the Allow index on metric VLDB property. You will study concepts such as level metrics, transformation. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Instead, it creates two passes of SQL and creates all SQL correctly except without an outer join to the lookup table in the final pass. Join common key on both sides. For information about accessing these properties, see the page reference for each property in the table below. Choose Data > Configure Bulk Export. How to change the syntax is described in detail by using examples. Check for VLDB properties tuning to see if SQL generation is using standards or best practice as per DB that we use (like Intermediate Table Type) Check individual pass by pass to see where the problem is. In the latter case, intermediate tables would be left on the database; administrators could remove them using a database-side scheduled task. For more details, go to Start -> Programs -> MicroStrategy -> Product Manuals -> Advanced Reporting Guide (PDF) -> 13. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". When selected, the options and SQL, if applicable, appear in the right side of the dialog box. Metrics using count or average, metrics with dynamic aggregation. The user should locate the last <Setting> XML entry in the file similar to the following entries:<Setting>The table b elow summarizes the MultiDimensional Expression (MDX) related VLDB properties. The VLDB properties at the different levels work together to affect report results. To view a summary of the system components that contain VLDB properties for a given report, select one of the system-level folders displayed under the VLDB Settings. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Open the Workstation window. 203 Exercise 7. 39 Intermediate Table Type VLDB property. A few common one are for Attribute or Metric join types, cross join check, type of intermediate table, etc. Select VLDB Properties from the Data menu. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. 2: Modifying join. Level dimensionality in a metric interacts differently with different features such as view filters, report filters, other metrics and certain VLDB properties. MicroStrategy application developers can further optimize SQL for their specific Oracle environment using these string insertion settings. Fact extensions may require subqueries, depending on their definition. Go to Metrics > NULL Check. A given VLDB setting. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Select the desired Property Value and repeat for other properties. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. Clear the Use default inherited value check box. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. (In MicroStrategy Developer, navigate to VLDB Properties > MDX > MDX Cell Formatting. 3. Navigate to 'Pre/Post Statements' and 'Report Pre Statement 1. 8/7/2021. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHyperIntelligence and its Architecture. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform14. There is a method to change the default syntax for table and column names while generating MicroStrategy SQL during report execution in MicroStrategy by using VLDB properties. The Microstrategy SQL that has been generated can be customized using the VLDB properties. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. 1. This article describes what the evaluation ordering property is in MicroStrategy 9. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Under 'Database instances', select VLDB Properties. Diagnosis. WHERE (col1, col2) in (SELECT s1. The attribute uses a CASE statement to replace NULL values with -999. pdf > VLDB Settings > VLDB properties > Query Optimizations > Dimensionality Model. . Group by column. See Details for All VLDB Properties for more information. For example, the report shown below ranks the NULL values. Modify the VLDB property you want to change. Most major databases have allowed the creation of special tables that have characteristics that separate them from 'normal' or 'permanent' tables in the. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base technical note: When the grand total metric and another metric exists on a grid, Cross Join is produced to join to grand total metric and is exempted from the Cartesian Join Governing property. These VLDB properties control the method by which the report data are normalized. pdf - MicroStrategy. This article describes best practices to be taken when connecting an instance of PostgreSQL in MicroStrategy. 1. •. In the Data Engine Version field, view and modify the Data Engine version. The XQuery Success Code VLDB property lets you validate Transaction Services reports that use XQuery. CAUSE: "SQL Global Optimization" under Query Optimizations is a hidden option that need to be made visible selecting "Show Advance Settings" under the menu option Tools in the VLDB. The user should locate the VLDB. From the Tools menu, select Show Advanced Settings. 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 >. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. Access the VLDB Properties Editor. 4. The "Evaluation Ordering" VLDB setting has two possible values, "6. This knowledge base article describes an issue in MicroStrategy 10. For steps, see the MicroStrategy Developer help. After the project information is processed, you are returned to MicroStrategy Developer. These VLDB properties control the method by which the report data are normalized. In MicroStrategy Developer versions prior to 9. If necessary, you can ensure that a property is set to the default. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. Check the SQL generated by MSTR is good (without cross joins) Check for the execution plan on database. Database instances for the project source are displayed. You can set additional metric VLDB properties at other levels, such as the report and project levels. <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. These settings are available only if the drill path destination is a template. 5 From the Data menu, select VLDB Properties. For steps, see the Upgrade Guide.