Any existing projects will retain the null checking behavior that was. The privileges are grouped by privilege type: Web Reporter privileges. One might be yours!Victoria Homes by Postal Code. Web Analyst privileges. MicroStrategy Office privileges. See Details for All VLDB Properties for more information. Exporting Report Results from MicroStrategy: Export Engine. ) Microstrategy Desktop. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. The VLDB Properties Editor opens. Visit REALTOR. The recommended VLDB optimizations for Teradata 12 (and higher) are listed below. If you choose Temp Table Join. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. Use Case Statement option available in VLDB Properties, If your report contains any Custom Groups. 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). Follow the steps below to change the property. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. This article describes what the evaluation ordering property is in MicroStrategy 9. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. In the Source area, select a database instance for the database to access using Freeform SQL. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. VLDB properties cannot be modified from MicroStrategy Web. 192 Determining the level to apply a VLDB property. Both properties are located in the Query Optimizations folder in the VLDB property editor. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. 1 and 10. 4. Victoria's peaceful atmosphere and vibrant real estate market make it a great place to search for your next home. Under VLDB Settings, navigate to the desired VLDB option. VLDB properties are usually determined by an administrator, but some may also be defined by a project’s designer. You're in the right place for real estate! 464 homes for sale in Victoria, BC are available on Point2. x report for a specific attribute using an ApplySimple statement as one of its forms. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. <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. Click Save and Close. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. Metrics using count or average, metrics with dynamic aggregation. Total views 28. The display format for dates does not change even after changing the SQL Date format and Date Pattern settings under VLDB properties of the project in MicroStrategy Developer. See the Advanced Reporting Guide. From the Tools menu, select Create VLDB Settings 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. In the VLDB Properties window, expand the folder called. Use this section to learn about the VLDB properties before modifying any default settings. 3. Default VLDB properties are set according to the database type specified in the database instance. 3) In Joins, select Join Type. The following list summarizes the metric-specific VLDB properties that can be set at the metric level. Join common key on both sides. The Project-Level Very Large Database (VLDB) Property setting, found in Joins > Preserve All Lookup Table Elements, 'Preserve lookup table elements joined to final pass result table based on template attributes with filter' is not turned on, which results in. MicroStrategy 9. In the VLDB Editor open the 'Tables' folder and click on 'Intermediate Table Type. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the. For example, the report shown below ranks the NULL values. Victoria is a good city to buy a house in for those who prefer a slower-paced atmosphere. The Database instances - SQL Data warehouses pane displays. 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. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". When the VLDB property Intermediate Table Type is set to "True Temporary Table", each pass results in a local temporary table. 1. Other VLDB Properties are mentioned below. 1, it is possible to identify specific attributes as having an incomplete lookup table by setting the “Preserve all final pass result elements” VLDB property within the attribute. You can specify another. What are the various ways of incorporating security in Microstrategy? 40. 4. Any projects that existed prior to upgrading metadata to MicroStrategy 2020 retain their original VLDB property settings. x and later). When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. 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. 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. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategyMicroStrategyEnginesAndSQL 11 2 1. Log in to a project in MicroStrategy Developer. MicroStrategy Transaction Services and XQuery allow you to access. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. 9 Name the report Indexing Analysis. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. 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. 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. MicroStrategy implements a list of strategies through VLDB settings to generate temp table for the efficient execution of complex business queries. The properties are saved in different folders, as indicated in the previous list. The reports created from an intelligent cube do not have this VLDB property used in normal reports. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Changes made to this VLDB setting can cause differences to appear in your data output. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. In Developer, right-click the report to set the limit for and select Edit. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. In MicroStrategy Developer, open a report in the Report Editor. ) From the Tools menu, select Show Advanced Settings. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. 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. 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. Project. 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. ACTIONWith MicroStrategy, a VLDB property exists for reports executing against MDX data sources. The "Evaluation Ordering" VLDB setting affects the order in which the Analytical Engine will perform various calculations. If necessary, you can ensure that a property is set to the default. The Intermediate Table Type property specifies what kinds of intermediate tables are used to execute the report. The Grouping panel is displayed. Click VLDB Properties. Property owners benefit from a fair number of nearby clothing stores. In the confirmation window that appears, click Yes. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". Right-click on the project and select 'Configure project'. It also displays all current settings for each VLDB property. The Database Instances Editor opens. 0, a VLDB property is available to control. Upgrading Your Database Type Properties. x, "Use relational model" is selected by default. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. 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. Additionally, the COALESCE function can be included in the SQL query. 👉 Free PDF Download: Microstrategy Interview Questions & Answers. ca. To configure it, open the Project. 4. x. Pages 100+ Identified Q&As 2. Character. Web Professional privileges. As mentioned, these steps will need to be done for each report that sorting in this way is desired. •. •[COUNTRY_ID] exists in the lookup table and this table is already present in the FROM clause, so it can indeed be extracted from the lookup table. For steps, see the Upgrade Guide. 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. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. x, select 'Project Documentation' from the Tools menu to start the wizard. For information about accessing these properties, see. 1 and 10. This section includes the following. 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. x. To the right of the Database connection area, click Modify. (0 = time limit not enforced by this governing setting)The MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. Under the VLDB properties for the report, change the Additional Final Pass Option setting to One. Local temporary tables, indicated with the "#" character, are stored in tempdb and incur less overhead. . 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. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. Enable. Make sure the Use default inherited value check box is cleared. 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. The VLDB property, Attribute to Join When Key From Neither Side can be Supported by the Other Side becomes obsolete once you upgrade your data engine version to 2021. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. 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. These properties apply only to MDX cube reports using data from an MDX cube. This information is available for each property in the VLDB Properties dialog box at each level. It is strongly encouraged that you post your questions on the community forum for any community. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. Level dimensionality in a metric interacts differently with different features such as view filters, report filters, other metrics and certain VLDB properties. VLDB is an acronym for You answered: Very Large Database Incorrect Correct answer: Very Large Database properties 13. MicroStrategy application developers can further optimize SQL for their specific Oracle environment using these string insertion settings. From the Data menu, select VLDB Properties. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. 5. VLDB properties also help you configure and optimize your system. 3. Parallel Query Execution is an advanced property that is hidden by default. Choose the database instance and then open VLDB Properties. Click Save and Close to save your changes. The solution is to backup old registry keys and re-generate default ones. Choose one of the following: •. QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. 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. Choose Data > Configure Bulk Export. . The VLDB Properties Editor opens. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. 3. Right-click a database instance and select Edit. This property overrides the Number of report result rows. The options for this. The Results Set Row Limit VLDB property is used to limit the number of rows returned from the final results set SELECT statements issued. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. Since MicroStrategy Analytical Engine 9. Clear the Use default inherited value check box. One of the options under Analytical Engine folder is called "Metric Level Determination. 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 recommended VLDB optimizations for Teradata 12. x, select 'Project Documentation' from the Tools menu to. For an Intelligent cube or incremental refresh report, right-click it and choose Edit. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. ; Click the General tab. There are number of them. In MicroStrategy Developer, choose File > New > Report. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. See the warning above if you are unsure about whether to set properties to the default. MicroStrategy periodically updates the default settings as database vendors add new. Additional details about each property, including examples where necessary, are provided in the sections following the table. MicroStrategy can support multiple (more than 5) pre-statements to put in a report. 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. The VLDB Properties Editor opens. 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. 201 Modifying VLDB properties at the report level. The VLDB Properties Editor opens. Possible locations for VLDB optimizations in the query structure are listed below. A given VLDB setting. This article describes best practices to be taken when connecting an instance of PostgreSQL in MicroStrategy. MicroStrategy SQL Generation Engine 9. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. 1, the VLDB property ‘Analytical Engine > ‘Filtering on String Values’ has been available at project level. The Project-Level Very Large Database (VLDB) Property setting, found in Joins > Preserve All Lookup Table Elements, 'Preserve lookup table elements joined to final pass result table based on template attributes with filter' is not turned on, which results in the filters being ignored. They are exactly the same. Select the desired Property Value and repeat for other properties. •. In the Database Instance Manager, right-click on the database instance used by the MicroStrategy Tutorial Project (by default, this would be ‘Tutorial Data’) and select VLDB Properties. The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. 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. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. The Dimensionality Model property is strictly for backward compatibility with MicroStrategy 6. Contact MicroStrategy. x For MicroStrategy reports that generate multi-pass SQL with temporary tables, it is sometimes desired that that description form of an attribute is also selected in the temp table along with the ID form. Right-click a database instance and select Edit. 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. 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. In the bottom left corner, click on the button "Generate Connection File". For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. A report is generated that displays all VLDB properties available at the level from which you accessed the VLDB Properties Editor. See Template Editor. Loading × Sorry to interruptPlaces to Set VLDB Properties. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. Intermediate Table Type . The VLDB Properties Editor opens. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. At the report level, change the. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. 8/7/2021. x introduces a third option to the VLDB Property "Drop Temp Table Method. 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. Database Instance Level This is the most common place to set VLDB Properties. Open the VLDB Properties Editor this way. 4. Additional VLDB Settings. In Web: Click the MicroStrategy > Preferences. Group by alias. If the report result set exceeds the limit specified in the Result Set Row Limit, the report execution is terminated. 1 and 10. 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. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. Parallel Query Execution is an advanced property that is hidden by default. 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. These settings are available only if the drill path destination is a template. For a project, right-click it and choose Advanced Properties. How to change the syntax is described in detail by using examples. 4. The attribute uses a CASE statement to replace NULL values with -999. STEPS TO REPRODUCE: In Web, create a report with the attributes Customer Region, Category,. See the warning above if you are unsure about whether to set properties to the default. ; 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. pdf), Text File (. x, users notice that Null checks are ignored in the HAVING clause when the VLDB property "change the Additional Final Pass Option" is set to "One additional final pass only to join lookup tables". For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. To address this issue, a VLDB property called "Downward Outer Join" should be used. Double-click Time to open the folder, then double-click Year. Viewing and Changing VLDB Properties. This is reflected in the checkbox “Use default inherited value for all VLDB properties”. The two possible values are as. You can determine the default options for each VLDB property for a database by performing the steps below. MDX cubes are also referred to as MDX cube sources. The MicroStrategy platform provides VLDB settings for all supported RDBMS platforms to generate optimized SQL that takes advantage of database-specific functionality. x has changed the default value of the "SQL Global Optimization" VLDB property. An example is: \MicroStrategy Tutorial\Public Objects\Reports\MicroStrategy Platform Capabilities\Ad hoc Reporting\Sorting\Yearly Sales!i inserts the job priority of the report which is represented as an integer from 0 to 999 (can be used in all Pre/Post statements). This. Parallel Query Execution. •. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. From the Data menu, choose VLDB Properties. Change the VLDB setting . If an environment does not already exist, an environment will need to be created first. Beginning with MicroStrategy SQL Engine 9. Certain VLDB properties use different default settings depending on which data source you are using. x? This article explains the usage of the Attribute Selection Option for Intermediate Pass’ VLDB property, which allows the user to select additional attributes in intermediate SQL passes. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". The Project Configuration Editor opens. Under Query Optimizations, select SQL Global Optimization. On MicroStrategy Web and Workstation, the same. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. Under VLDB Settings, navigate to the desired VLDB option. Under 'Database instances', select VLDB Properties. This setting is called Join Across Datasets. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. Properties set at the report level override properties at every other level. (The original name for this property, in fact, was "Incomplete lookup table. The most basic DBMS (database) level where properties are defined. By rendering data in smaller slices, the incremental fetch setting in MicroStrategy Web can help significantly reduce the user wait times, while still handling the display of large result sets. You can configure this setting. This article covers the purpose of the where clause driving table property. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. The Use default inherited value option indicates the level that is active, while the SQL preview box displays a description of the selected setting. On the Advanced tab, select the Use parameterized queries check box. . In MicroStrategy Developer, from the File menu, point to New, and select Transformation. Then select MDX metric values are formatted by column (default) or MDX metric values are formatted per cell. 2. 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. . 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. MicroStrategy Analytical Engine 9. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. Viewing VLDB properties. 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. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. The Grouping Properties dialog box opens. Check the option according to the database used. Disallow joins based on unrelated common attributes. Group by position. But the grid is not reset properly when adding and removing a derived element. x. Accessing Report VLDB Properties. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. At the bottom of the Options and Parameters area for that. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". The attribute level follows a consecutive order from. 1, VLDB properties may be enabled in Intelligent Cube reports and user reports to include Dynamic Sourcing diagnostic messages in SQL View. 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. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. 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. This article explains the behavior of the commit level VLDB propertyThe post-execution SQL that was available in Narrowcast can be replaced by implementing post-report SQL VLDB properties. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. Description. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. This feature provides the ability to create multiple query queues and queries are routed to an appropriate queue at runtime based on their user group or query group. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Specifying the Display Mode and VLDB Properties. You will study concepts such as level metrics, transformation. NIT Rourkela. This article describes the best practices to be taken when connecting an instance of Azure Synapse Analytics in MicroStrategy. 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. 3. Export to exports the report to Microsoft Excel, Microsoft Word, Microsoft Access, a text file, an HTML file, or a PDF file. 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. In the Project-Level VLDB settings area, click Configure. 5. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. . Remove the training metric from the report. '. To the right of the Database connection area, click Modify. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the (missing or bad snippet) for steps to set this VLDB property. The image below shows how this hierarchy is populated on a report in. VLDB properties allow you to customize the SQL that MicroStrategy generates. Expand the 'Administration' Icon, and select the Database Instance Manager. Go to the 'Data' menu and select 'VLDB Properties'. 10 Snowflake Derived Tables require non-standard Outer Join VLDB property settings. 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 VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Viewing and Changing VLDB Properties. 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. Choose Tools > Show Advanced Settings option if it is. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Additional details about each property, including examples where necessary, are provided in the sections following the table. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. 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. . Parallel Query Execution. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. Open MicroStrategy Developer. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. These settings are available only if the drill path destination is a template. Read/write-optimized tree indexing for solid-state drives. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. Project-Level VLDB settings: Click to configure the analytical engine settings. VLDB Properties, available to users with Developer privileges, opens the VLDB Properties (Report) dialog box, which allows you to apply VLDB properties to the report's SQL. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. 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. For more details, go to Start -> Programs -> MicroStrategy -> Product Manuals -> Advanced Reporting Guide (PDF) -> 13.