For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. 3) In Joins, select Join Type. A given VLDB setting. Preview Feature: Create and edit reports with your favorite features including the Advanced Properties panel, View Filters, SQL View, and many more. These tables can either be 'permanent' or 'true temporary'. How to create a MicroStrategy connection file (. The VLDB Properties Editor opens. The most basic DBMS (database) level where properties are defined. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. Solutions available. In MicroStrategy Developer, browse to an attribute, then right-click the attribute and select Edit. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. You must have the " Use VLDB property editor " privilege to make changes to the setting. Only project configured with those setting is applicable for the case in this article. 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. Description Understanding your data characters and choosing the matched. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. 1 and 10. 9 Name the report Indexing Analysis. 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. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. Under Categories, expand Calculations, and select Attribute Join Type. When the VLDB property Intermediate Table Type is set to "True Temporary Table", each pass results in a local temporary table. The VLDB Properties Editor opens. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. 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. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. The. x. To create a last year transformation based on an expression. This setting is called Join Across Datasets. 10 Snowflake Derived Tables require non-standard Outer Join VLDB property settings. MicroStrategy SQL Generation Engine 9. The options for this. Other VLDB Properties are mentioned below. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". 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. Viewing and Changing VLDB Properties. If necessary, you can ensure that a property is set to the default. 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. In the VLDB Properties window, expand the folder called. The Microstrategy SQL that has been generated can be customized using the VLDB properties. For this reason, two additional options are provided:Export to PDF: export a report or document to a PDF document: EXPORTTOPDF:. These settings are passed to the specific report/job VLDB properties only from the project primary database instance. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. MicroStrategy 9. xml file in the "Program Files (x86)Common FilesMicroStrategy" folder on a machine with MicroStrategy Developer installed and create a backup of this file, and then edit it. 8/7/2021. Use VLDB property editor: use the VLDB Properties Editor: USEVLDBEDITOR: View ETL information:. DeanElectronHummingbird14. x has changed the default value of the "SQL Global Optimization" VLDB property. x, outer joins are designed to get all the data from the lookup tables. x, the only options were to drop tables or do nothing. Beginning with MicroStrategy 8. . In MicroStrategy Developer, log in to a project. Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. 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. 4. Specifying the Display Mode and VLDB Properties. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. DATA ANALYSIS. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. This VLDB setting is located in the 'Indexing' folder and has the following options:In MicroStrategy Web, open the document in Design or Editable Mode. Loading × Sorry to interruptPlaces to Set VLDB Properties. It is recommended to always enable secure text input. Number of Views 948. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. x, "Use relational model" is selected by default. If you choose Temp Table Join. 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. In this example, the raw ID is used. Changes made to this VLDB setting can cause differences to appear in your data output. Temporary Table. The new setting is a Database Instance level VLDB property called Default Sort Behavior for Attribute. Both properties are located in the Query Optimizations folder in the VLDB property editor. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. Refer to the MicroStrategy System Administration Guide for a detailed description of these properties. 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. The reports created from an intelligent cube do not have this VLDB property used in normal reports. The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3. In MicroStrategy 2020 Update 2, a new VLDB Property, Cartesian Join Governing, exists on the Project, Report, Dataset, and Visualization level. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. 3. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. This issue has been addressed starting in MicroStrategy 9. The attribute opens in the Attribute Editor. Expand the Governing settings, then select Results Set Row Limit. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. Property owners benefit from a fair number of nearby clothing stores. For a data source, right-click it and choose Edit. Controls whether two fact tables are directly joined together. Check the SQL generated by MSTR is good (without cross joins) Check for the execution plan on database. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. 201 Modifying VLDB properties at the report level. How to change the syntax is described in detail by using examples. 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. Default VLDB properties are set according to the database type specified in the database instance. For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. mstr) files that can be sent through Distribution Services is defined by the MicroStrategy (. 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. To set these properties, open the report in the Report Editor or Report Viewer. The maximum number of rows returned to the Server for the final result set. By default, they are defined by MicroStrategy, optimized for the database and its version. Order of Precedence. 0, a VLDB property is available to control. However, there is no governing for in-memory executions, including data blending which creates unnecessary risk to the stability and performance of the. CAUSE. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. 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. Open the report template in the Template Editor. In MicroStrategy Developer versions prior to 9. 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. By default, all properties are governed by the one at the top level. Scribd is the world's largest social reading and publishing site. One of the options under Analytical Engine folder is called "Metric Level Determination. Accessing Report VLDB Properties. In the lower-right. Open navigation menu. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. In MicroStrategy 7. KB11122: What is the “Downward Outer Join” VLDB property in MicroStrategy SQL Generation Engine? The downward outer join algorithm introduces a cost, in terms of performance and an inflated number of result rows, in exchange for improved data reliability. To remove the COALESCE function from the SQL generated by the MicroStrategy SQL Engine, perform one of the following actions: At the project level, change the VLDB property 'Full Outer Join Support' to 'No support' from the Database Instance's VLDB properties under the 'Joins' group. 3. (0 = unlimited number of rows; -1 = use value from higher level. mstrc) Open Workstation. Metrics using count or average, metrics with dynamic aggregation. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. The Data population for Intelligent Cubes VLDB property allows you to define if and how Intelligent Cube data is normalized to save memory resources. . Click Save and Close to save your changes. Dimensionality Model. From the Data menu, choose VLDB Properties. This is a Microstrategy way of handling database-specific preferences while generating the report SQL. Single SQL pass time-out in seconds. Each queue is defined by concurrency level, user groups, query groups, wild cards, memory percent to be used,. 3. 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. Click Save and Close to save your changes. Hierarchy 2: 4. 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. How to change the syntax is described in detail by using examples. Both the SQL Date Format and. VLDB_PROPERTY_NAME: The. pdf - MicroStrategy. Additional VLDB Settings. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. The table b elow summarizes the Export Engine VLDB properties. 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. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. To the right of the Database connection area, click Modify. Click Properties. The following settings are advanced properties which are. VLDB properties also help you configure and optimize your system. This allows SQL to be run after the report execution, and is not tied to the subscription. Click the "VLDB Properties. See the warning above if you are unsure about whether to set properties to the default. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. In addition, this release introduces new features across the analytics, mobility, and security platforms—making it easier for users to build applications faster. As mentioned, these steps will need to be done for each report that sorting in this way is desired. Open the database instance for the project. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. This property is report-specific. Click VLDB Properties. VLDB is an acronym for You answered: Very Large Database Incorrect Correct answer: Very Large Database properties 13. You can configure this setting. This information is available for each property in the VLDB Properties dialog box at each level. Published: 4월 6, 2017. 4. 2) In Joins, select Preserve all the final pass result elements. Choose Data > Report Data Options. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. Beginning with MicroStrategy SQL Engine 9. 1, the VLDB property ‘Analytical Engine > ‘Filtering on String Values’ has been available at project level. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. MicroStrategy Library. Below are the new features exclusive to. Possible locations for VLDB optimizations in the query structure are. You can manipulate things like SQL join types, SQL inserts,. See Viewing and Changing Advanced VLDB Properties for more information on how to display this property. Export to PDF filter summaries include the full attribute and metric names. For examples and details to enable these properties, see SQL Generation and Data Processing: VLDB Properties. However, you want to show all the store. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Below are the list of parameters that the URL must. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform14. x. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. ")This is a known issue prior to MicroStrategy SQL Engine 9. For steps, see the MicroStrategy Developer help. . pdf), Text File (. x, outer joins are designed to get all the data from the lookup tables. Intermediate Table Type . Parallel Query Execution is an advanced property that is hidden by default. After changing the options, check the query that will be created in SQL preview. 0. You can set additional metric VLDB properties at other levels, such as the report and project levels. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. 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. MicroStrategy periodically updates the default settings as database vendors add new. Doing so, we. See the warning above if you are unsure about whether to set properties to the default. For use cases, examples, sample code, and other information on every VLDB property, see Details for All VLDB Properties. Select the desired Property Value and repeat for other properties. Web Analyst privileges. 5. col1, s1. " Save and close. MDX cubes are also referred to as MDX cube sources. See How to Edit VLDB Settings in. Then set the apply filter options property to. The report SQL shows that the first metric is calculated at the level of Quarter (report. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. SUMMARY: This document shows one issue that a dvanced VLDB properties don't show up when "Show Advanced Settings" is enabled in MicroStrategy Developer 10. Subqueries (or correlated subqueries) are used infrequently but significantly in the MicroStrategy SQL Generation Engine. ca. Level Metric of Profit ignoring YearThe report uses explicit table creation (VLDB Properties > Tables > Table Creation Type); The report requires more than one pass of SQL; "True temporary" or "Permanent" tables are used for intermediate tables (VLDB Properties > Tables > Intermediate Table Type); A metric expression used in the report refers to objects with. Preserve Common Elements of Lookup and Final Pass Result Table (Default). For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. 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 specifies a default value for each database platform that will generate appropriate SQL for the database. From here there will be a section for Analytical engine VLDB properties and an option to "Configure". . Follow the steps below to change the property. The system reads them from the same location. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform Products; MicroStrategy ONE; AI & Augmented; Dossier; Library; Workstation; HyperIntelligence; Multi-Cloud; Embedded Analytics; Innovations; Futures. Edit the report. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. In order to export a document in excel format using the URL API, the executionMode must be set to 4. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results. The following list summarizes the metric-specific VLDB properties that can be set at the metric level. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. 8 From the File menu, click Save As. 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. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHyperIntelligence and its Architecture. For reports with several relationship filters, temporary table syntax may execute. x introduces a third option to the VLDB Property "Drop Temp Table Method. MicroStrategy’s VLDB driver for Azure SQL Data Warehouse is designed to use SQL DW-specific features when they lead to improved performance or analytical functionality. The setting is applied. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. 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. It sets the general standards. The Project Configuration Editor opens. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. If a table has been imported from only one database instance, the secondary database instance panel will be empty and disabled. To overcome these challenges, we first analyze a real-world query trace from Snowflake and compare its properties to that of TPC-H and TPC-DS. VLDB. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. 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). " Uncheck the "Use default inherited value" checkbox. Published: 4월 6, 2017. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. VLDB_PROPERTY_NAME: The. Accessing and Working with VLDB Properties. (The original name for this property, in fact, was "Incomplete lookup table. This article describes the best practices to be taken when connecting an instance of Azure Synapse Analytics in MicroStrategy. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. From the Tools menu, select Grouping. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. This information is available for each property in the VLDB Properties dialog box at each level. Lets you identify attributes that include empty elements, which can then be ignored when. Choose one of the following: •. Accessing Report VLDB Properties. Exporting Report Results from MicroStrategy: Export Engine. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. On the Freeform Sources tab, select Create Freeform SQL report. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". 199 Exercise 7. This article describes best practices to be taken when connecting an instance of PostgreSQL in MicroStrategy. col2…) While the default values should result in the. In MicroStrategy Developer 9. 2. •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 you change a VLDB property setting at the database instance or project level, you must restart Intelligence Server for the MicroStrategy Engine to read the latest schema information from the metadata. Certain attribute-to-attribute comparisons may require subqueries. You can specify another. 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. These settings are available only if the drill path destination is a template. •[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. Enable. You can connect to multiple projects on. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. Right-click a database instance and select Edit. 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. 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. Restart the Intelligence server to apply the changes. 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 example, ApplySimple("#0 * #1",[col1],[col2])indicates that two items, col1 and col2, referenced as. Allow joins based on unrelated common. Click Properties. •Students review the most commonly used VLDB properties in certain categories, such as indexing, joins, pre/post statements, query optimizations, and tables. You must have the "Use VLDB property editor" privilege to make changes to the setting. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. Victoria is a good city to buy a house in for those who prefer a slower-paced atmosphere. 1. It sets the general standards. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. a. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. In the Attribute Editor, on the Tools menu, select VLDB Properties. This occurs when the data type of the attribute is timestamp. At the report level, change the. 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. Go to the 'Data' menu and select 'VLDB Properties'. The VLDB properties are grouped into different property sets, depending on their functionality: Viewing and Changing VLDB Properties. Metric-specific VLDB properties that can be set at the metric level include. The VLDB properties at the different levels work together to affect report results. To configure it, open the Project. Dimensionality Model is an advanced property that is hidden by default. VLDB properties can provide support for unique configurations. Project-Level VLDB settings: Click to configure the analytical engine settings. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. It also displays all current settings for each VLDB property. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. The VLDB property's behavior will be demonstrated using the following attribute and report. VLDB properties allow you to customize the SQL that MicroStrategy generates. KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. Modify the VLDB property you want to change. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. On MicroStrategy Web and Workstation, the same. If you have selected multiple reports, including bulk export reports, and choose the Run Report option from the right-click menu, all the bulk export reports are filtered out and are opened in the Report Editor; the other reports. To view VLDB properties. Explain how you can optimize a report in Microstrategy? VLDB properties enable you to customize the SQL that Microstrategy produces, and determine how data is processed by the Analytical. Select either Disable or Enable depending on whether you want to disable or enable. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. (For information on object. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. the Report Data Options. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. Possible locations for VLDB optimizations in the query structure are listed below. The final pass will perform two operations. Upgrading Your Database Type Properties. •[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. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the business reports. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. Visit REALTOR. This feature is similar to what we see in. . Certain VLDB properties use different default settings depending on which data source you are using. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. In the Project Configuration Editor, expand Project definition, and select Advanced. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. Choose the database instance and then open VLDB Properties. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. For an Intelligent cube or incremental refresh report, right-click it and choose Edit. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. A few common one are for Attribute or Metric join types, cross join check, type of intermediate table, etc. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. VLDB properties allow MicroStrategy products to exploit the unique optimizations offered by different databases. Under 'Database instances', select VLDB Properties. On the Advanced tab, select the Use parameterized queries check box. Expand the folder to see what VLDB properties have been applied to that part of the system. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. This reads the settings from the updated DATABASE. Log in to a project in MicroStrategy Developer. The VLDB Properties Editor opens. This property is called 'MDX TopCount Support' and is available at the report level and database instance level.