Click Properties. Select Teradata V2R4 and move it to the right using the > button. Using the Select Statement Post String VLDB property, MicroStrategy can support this. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. In the confirmation window that appears, click Yes. MicroStrategy periodically updates the default settings as database vendors add new. MicroStrategy Advanced Reporting Guide provides comprehensive information on advanced topics for using the MicroStrategy query and reporting. These properties apply only to MDX cube reports using data from an MDX cube. 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. Web Analyst privileges. 1, the VLDB property ‘Analytical Engine > ‘Filtering on String Values’ has been available at project level. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. The following. pdf), Text File (. They can be set at different levels throughout a project to establish a specific behavior regarding the object type. Changing an option in one of the editors automatically reads the changes and is reflected in the other editor Certain VLDB properties use different default settings depending on which data source you are using. There are a number of them. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Attribute. select a11. One way to implement multi-pass SQL is to execute each pass (each query block) in a separate table. These properties apply only to MDX cube reports using data from an MDX cube. The Use default inherited value option indicates the level that is active, while the SQL preview box. One of the options under Analytical Engine folder is called "Metric Level Determination. VLDB properties are usually determined by an administrator, but some may also be defined by a project’s designer. In the Source area, select a database instance for the database to access using Freeform SQL. Accessing Report VLDB Properties. 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. The properties are saved in different folders, as indicated in the previous list. The Null Checking for Analytical Engine VLDB property determines whether or not null values are interpreted as zeros when the Analytical Engine calculates data. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Notice that the 4 options shown on the upper right are the same as those in the VLDB dialog box (internally they are read from the same location). . The system reads them from the same location. Modify the VLDB property you want to change. KB441418: Supplemental reference for installing Hotfix on MicroStrategy version 10. 1: Creating a report with missing aggregated values. Check the report SQL again, observe that "with" clause (aka common table expression) is applied. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Database instances for the project source are displayed. x has changed the default value of the "SQL Global Optimization" VLDB property. To begin, the architecture for dashboard execution is. •. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. Allows the MicroStrategy SQL Engine to use a new algorithm for evaluating whether or not a Cartesian join is necessary. The option "SQL Global Optimization" under Query Optimizations is not available when a report VLDB properties need to be changed. MicroStrategy 9. On the Advanced tab, select the Use parameterized queries check box. Group by alias. 4. The VLDB Properties Editor opens. 3. List all parent groups of a user group 'sGroup'. wanttobuildandresellMicroStrategy-basedproductsorapplicationssuitedto particularindustries. The Grouping Properties dialog box opens. For use cases, examples, sample code, and other information on every VLDB property, see Details for All VLDB Properties. 3. 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. OR. txt) or read online for free. Project-Level VLDB settings: Click to configure the analytical engine settings. Deliveries privileges. See Template Editor. Because of the impact, the VLDB Property, Cartesian Join Warning, introduced in MicroStrategy 2020 Update 2 exists to protect the system in Live Connect to Project Schema scenarios. You can configure properties. 6 :Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. The Preserve All Lookup Table Elements VLDB property is used to show all attribute elements that exist in the lookup table, even though there is no corresponding fact in the result set. ACTIONWith MicroStrategy, a VLDB property exists for reports executing against MDX data sources. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. pdf - MicroStrategy. •The Preserve All Lookup Table Elements VLDB property is used to show all attribute elements that exist in the lookup table, even though there is no corresponding fact in the result set. 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" as shown below: However, the images in the report display properly when the report is executed in. Click on the upgrade button. For users with environments and metadata updated to MicroStrategy 2020, the Analytical Engine will ignore null values for aggregation functions in new projects by default. 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. This technical article explains expected new behavior in MicroStrategy 10. You can determine the default options for each VLDB property for a database by performing the steps below. 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. If the size for a SQL pass. Set the additional final pass property to force an additional pass of SQL. Viewing and Changing VLDB Properties. 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. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. Restart the Intelligence server to apply the changes. The Year - Define a new member attribute. For reports with several relationship filters, temporary table syntax may execute. If an environment does not already exist, an environment will need to be created first. If a table has been imported from only one database instance, the secondary database instance panel will be empty and disabled. 3. On the Freeform Sources tab, select Create Freeform SQL report. In MicroStrategy 10. 1 and 10. pdf), Text File (. The Database Connections dialog box opens. (For information on object. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Right-click on the report and click on the 'Edit' menu. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. If you choose Temp Table Join. . From the Data menu, select VLDB Properties. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping 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. MicroStrategy added an Advanced Properties dialog that includes elements formerly know as VLDB properties, as well as other items including report data properties such as Evaluation Order. 2: Modifying join. 1 and 10. On the Advanced tab, select the Use parameterized queries check box. 7 regarding null checking performed by the Analytical Engine. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. However, you want to show all the store. This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategy. VLDB properties allow you to customize the SQL that MicroStrategy generates. It is strongly encouraged that you post your questions on the community forum for any community. 1 and 10. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. Use the SQL Date Format VLDB property to format the date string to match the attribute's description (MEMBER_NAME property in the cube). Choose Data > Configure Bulk Export. For information on VLDB properties, including steps to access and modify them for various MicroStrategy objects, see the System Administration Guide: If you define the Null checking for Analytical Engine property as True, NULL values are treated as zero values in the rank calculation. The image below shows how this hierarchy is populated on a report in. 2. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. In the Project-Level VLDB settings area, click Configure. Below are the new features exclusive to. By default, all properties are governed by the one at the top level. Each queue is defined by concurrency level, user groups, query groups, wild cards, memory percent to be used,. 1, VLDB properties may be enabled in Intelligent Cube reports and user reports to include Dynamic Sourcing diagnostic messages in SQL View. In Web: Click the MicroStrategy > Preferences. ' 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. 8 From the File menu, click Save As. 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. !o inserts the report name (can be used in all Pre/Post statements). For more details, go to Start . " Save and close. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHyperIntelligence and its Architecture. x order - Calculate. KB40199: "The tokens 'NTLINK' and 'IMPORTWINUSER' should not be used. col1, s1. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. 3) Explain how intelligent cubes are different from ordinary cubes?. (This exception case is supported in MicroStrategy 2020 Update 5 and above, MicroStrategy 2021. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. In the Results Set Row Limit field, type the limit. The method used for multiple data source access is controlled by a project-level VLDB Property. . Different scenarios will be explored throughout this article to better understand the logic of how MicroStrategy is working. Group by alias. Certain VLDB properties exist at the database instance level but are viewed by the SQL Engine as unrelated to the database used. The Intermediate Table Type property specifies what kinds of intermediate tables are used to execute the report. The “#n” code in Apply function syntax serves as placeholders for the MicroStrategy objects being passed to your database. Access the VLDB Properties Editor. See Details for All VLDB Properties for more information. QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. Choose Data > Configure Bulk Export. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. Property Type. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. The Table Creation Type property tells the SQL Engine whether to create a table implicitly or explicitly. Preview Feature: A new data. Export a Report Services document to Excel with formatting using URL API in MSTR Web. Open your report in the Report Editor. See the screenshot below:In the Select Configuration dialog, go to Project definition > Advanced. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. The maximum number of rows returned to the Server for the final result set. You can use this setting on the following levels: Project level; Report level; Dossier visualization levelWhy MicroStrategy Why MicroStrategy; Customer Stories; Platform45+ [REAL-TIME] MicroStrategy Interview Questions & Answers - Free download as PDF File (. This file can be modified to add additional VLDB properties to display in case non standard properties need to be changed in an environment. In this example, the raw ID is used. Default VLDB properties are set according to the database type specified in the database instance. for more information on this setting. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. You can determine the default options for each VLDB property for a database by performing the steps below. VLDB properties also help you configure and optimize your system. However, this could produce inflated subtotal or dynamic. List Projects That User Has Access ToInformation and instructions for MicroStrategy administrative tasks such as configuring VLDB properties and defining data and metadata internationalization, and reference material for other administrative tasks. " Uncheck the "Use default inherited value" checkbox. Single SQL pass time-out in seconds. By default, they are defined by MicroStrategy, optimized for the database and its version. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. This article covers the purpose of the where clause driving table property. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. VLDB properties can provide support for unique configurations. . MicroStrategy Transaction Services and XQuery allow you to access. Temporary Table. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. XQuery Success Code is an advanced property that is hidden by default. A given VLDB setting can support or. QUARTER_ID QUARTER_ID, KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. Parallel Query Execution is an advanced property that is hidden by default. Use this section to learn about the VLDB properties before modifying any default settings. This VLDB property determines how MicroStrategy joins tables with common columns. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. MicroStrategy SQL Generation Engine 9. MicroStrategy Analytical Engine 9. In MicroStrategy Developer, browse to an attribute, then right-click the attribute and select Edit. 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. DATA ANALYSIS. The index for referencing these objects begins with 0 and increases by for each successive object passed. 1 and 10. Solutions available. Right-click on the report and click on the 'Edit' menu. The following settings are advanced properties which are. Project-Level VLDB settings: Click to configure the analytical engine settings. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. The VLDB properties at the different levels work together to affect report results. x. SYMPTOM: To fix the issue mentioned in KB30419 the VLDB property "Include higher-level related attribute in metric level (deprecated)" is applied to the report. Check the option according to the database used. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. You will study concepts such as level metrics, transformation. x, the only options were to drop tables or do nothing. 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. x or earlier. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. If this VLDB property is not displayed, you must upgrade the project metadata. The Grouping panel is displayed. SQL Global Optimization This setting can reduce the number of SQL passes generated by MicroStrategy. For example, if a VLDB property is set one way for a report and the same property is set differently for the database instance, the report setting takes precedence. As shown below, for a specific report, the 'Group By ID Attribute' VLDB property is set to 'Group by column' instead of 'Group by expression' to avoid using an ApplySimple. ) Microstrategy Desktop. 3. 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. " The default value here is "Include only lowest-level attribute in metric level (recommended for version 9. MicroStrategy implements a list of strategies through VLDB settings to generate temp table for the efficient execution of complex business queries. The VLDB Properties Editor opens. Dimensionality Model is an advanced property that is hidden by default. ; Click the General tab. In MicroStrategy 7. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. A report is generated that displays all VLDB properties available at the level from which you accessed the VLDB Properties Editor. 203 Exercise 7. 3. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. 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 can support multiple (more than 5) pre-statements to put in a report. 3. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. 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. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. You can manipulate things like SQL join types, SQL inserts, table creation properties, and so on. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. Understanding your data characters and choosing the matched configuration could enhance the performance and accelerate the process to view the latest data. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. 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. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. This article addresses the change made to the Downward Outer Join setting. To address this issue, a VLDB property called "Downward Outer Join" should be used. . 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. Choose Tools > VLDB Properties. 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. Click VLDB Properties. You can set additional metric VLDB properties at other levels, such as the report and project levels. link MicroStrategy users and groups to users and groups from sources such as Windows NT, LDAP, or a database:VLDB properties allow you to customize the SQL that MicroStrategy generates. In the Data Engine Version field, view and modify the Data Engine version. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. For steps, see the Upgrade Guide. The VLDB Properties Editor opens. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Beginning with MicroStrategy 8. These values are set by default when the "Oracle 11g" database object is used (set at Configuration Managers > Database Instances > Database Instance > Database connection Type ). 2) In Joins, select Preserve all the final pass result elements. This article covers the purpose of the where clause driving table property. Certain VLDB properties use different default settings depending on which data source you are using. When VLDB settings are configured at the report level to allow for an outer join to the lookup table in MicroStrategy Developer, the SQL does not show an outer join. This article describes best practices to be taken when connecting an instance of PostgreSQL in MicroStrategy. When an Intelligent Cube is published, the description information for the attributes (all data mapped to non-ID attribute forms) included on the Intelligent Cube is repeated for every row. 3. Published: 4월 6, 2017. This property limits the maximum amount of rows to 80,000. x order - Calculate. x and 10. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. These values are set by default when the "Teradata 12" database object is used (set at Configuration Managers > Database Instances > Database Instance. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. Within here there are. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. See KB484738 for more information. 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. This occurs when the data type of the attribute is timestamp. 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. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. 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. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. Change the VLDB setting . For an Intelligent cube or incremental refresh report, right-click it and choose Edit. Hierarchy 2: 4. From the Tools menu, select Set all values to default. See Viewing and Changing Advanced VLDB Properties for more information on how to display this property. For example, ApplySimple("#0 * #1",[col1],[col2])indicates that two items, col1 and col2, referenced as. b. Report Level: Data -> VLDB Properties Unhide Parallel Options: Tools -> Show Advanced Settings Other VLDB settings that affect query generation. Clicking in Preserve all pass the final elements option. en Change Language. ) From the Tools menu, select Show Advanced Settings. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. Right-click a database instance and select Edit. VLDB_PROPERTY_NAME: The name of the property, returned as a string. From the Data menu, choose VLDB Properties. It has the following five options:What are VLDB properties? VLDB stands for Verly Large Data Base Properties. Relationship Tables 4. List Parent User Groups. Under Categories, expand Calculations, and select Attribute Join Type. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. The. Expand the 'Administration' Icon, and select the Database Instance Manager. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. Total views 28. These values are set by default when the "Oracle 11g" database object is used (set at Configuration Managers > Database Instances > Database Instance > Database connection Type ). In our current design, report pre/post statement 5 is different from 1-4. For information about accessing these properties, see. . Accessing and Working with VLDB Properties. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. The table b elow summarizes the MultiDimensional Expression (MDX) related VLDB properties. Open the report template in the Template Editor. Expand the 'Governing' folder and select 'SQL Time Out (Per Pass). Non-aggregable metrics, in which a metric specifies a dimensional attribute with a grouping level of beginning (fact), ending (act), beginning (lookup), or ending (lookup). (0 = unlimited number of rows; -1 = use value from higher level. The properties are saved in different folders, as indicated in the previous list. Group by position. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. The most basic DBMS (database) level where properties are defined. You're in the right place for real estate! 464 homes for sale in Victoria, BC are available on Point2. In the bottom left corner, click on the button "Generate Connection File". To be effective. Accessing Report VLDB Properties. For a project, right-click it and choose Advanced Properties. "The table below summarizes the Joins VLDB properties. These settings affect how MicroStrategy Intelligence Server. A given VLDB setting. •. ")This is a known issue prior to MicroStrategy SQL Engine 9. Specifying the Display Mode and VLDB Properties. 4. Project. Details of Document Execution Request, introduce the Performance Troubleshooting Cycle, and present links to other resources with detailed steps for troubleshooting specific components that may affect performance. STEPS TO REPRODUCE: In Web, create a report with the attributes Customer Region, Category,. In Developer, right-click the report to set the limit for and select Edit. This information is available for each property in the VLDB Properties dialog box at each level. 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. See the Advanced Reporting Guide. To configure it, open the Project. 4. 4. 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. Additional details about each property, including examples where necessary, are provided in the sections following the table. A given VLDB setting can support or. Disallow joins based on unrelated common attributes. Use VLDB property editor: use the VLDB Properties Editor: USEVLDBEDITOR: View ETL information:. Expand the Database instances folder. 1, this can be done at the report level by following the steps in technical note 10073. Click the Joins folder to expand it and then choose Preserve all lookup table elements. 0. VLDB properties allow MicroStrategy products to exploit the unique optimizations offered by different databases. 1 and 10. Expand the Governing settings, then select Results Set Row Limit. This controls whether the MDX function TopCount is used in place of Rank and Order to support features such as metric qualifications. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Exporting Report Results from MicroStrategy: Export Engine. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. col1, s1. One might be yours!Victoria Homes by Postal Code. The recommended VLDB optimizations for Oracle 11g are listed below. What ensures that object definitions are kept consistent and accurate across all environments when objects are migrated from a testing environment to a production environment You answered: Migration manager Incorrect Correct. ; Click the General tab. The Preserve all lookup table elements. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. 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. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. For steps, see the MicroStrategy Developer help. The "Evaluation Ordering" VLDB setting has two possible values, "6. Metrics using count or average, metrics with dynamic aggregation. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. For new installations of MicroStrategy 8. There are a number of them. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. Database Instance Level This is the most common place to set VLDB Properties. 1 and 10. ; Click the General tab. This allows SQL to be run after the report execution, and is not tied to the subscription. This is reflected in the checkbox “Use default inherited value for all VLDB properties”.