4. KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. The fact columns can also be included in the primary index, using the Allow index on metric VLDB property. If excutionMode is not provided in the URL, by default PDF will be used as executionMode. In MicroStrategy Developer, log in to a project. These settings are available only if the drill path destination is a template. 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. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. The default option is for aggregation calculations to ignore nulls and for scalar calculations to treat null values as zero. col2…) While the default values should result in the. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. (In MicroStrategy Developer, navigate to VLDB Properties > MDX > MDX Cell Formatting. Diagnosis. VLDB properties allow MicroStrategy products to exploit the unique optimizations offered by different databases. Web Professional privileges. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. This setting is called Join Across Datasets. 195 Managing joins in a non-uniform hierarchy. 4. Navigate to 'Pre/Post Statements' and 'Report Pre Statement 1. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. Web Analyst privileges. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. This property is report-specific. Properties set at the report level override properties at every other level. Property Type. Modify the VLDB property you want to change. 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. Contact MicroStrategy. 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. pdf), Text File (. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. See the Advanced Reporting Guide. 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". This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategy. Admin. In the Project-Level VLDB settings area, click Configure. (This exception case is supported in MicroStrategy 2020 Update 5 and above, MicroStrategy 2021. x. This occurs when the data type of the attribute is timestamp. What are the various ways of incorporating security in Microstrategy? 40. Double-click Time to open the folder, then double-click Year. From the Tools menu, select Set all values to default. 4. 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. •[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. 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. MicroStrategy Transaction Services and XQuery allow you to access. Use Case Statement option available in VLDB Properties, If your report contains any Custom Groups. Database instances for the project source are displayed. Click on. For a project, right-click it and choose Advanced Properties. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. VLDB_PROPERTY_NAME: The name of the property, returned as a string. Topics Introduction to the MicroStrategy engine Basic optimizations Templates Metrics Filters The. It is available at multiple levels such as Project level, Database Instance level , metric, report, template etc. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. 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. The attribute uses a CASE statement to replace NULL values with -999. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. 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. SQL Global Optimization This setting can reduce the number of SQL passes generated by MicroStrategy. 2. However, you want to show all the store. For example, the report shown below ranks the NULL values. To the right of the Database connection area, click Modify. See Details for All VLDB Properties for more information. The recommended VLDB optimizations for Teradata 12. Select the desired Property Value and repeat for other properties. Follow the steps below to change the property. The "Evaluation Ordering" VLDB setting affects the order in which the Analytical Engine will perform various calculations. To create a last year transformation based on an expression. Accessing and Working with VLDB Properties. The attribute level follows a consecutive order from. DeanElectronHummingbird14. MicroStrategy Office privileges. One of the options under Analytical Engine folder is called "Metric Level Determination. In Developer, right-click the report to set the limit for and select Edit. Under Query Optimizations, select SQL Global Optimization. This property overrides the Number of report result rows. In the latter case, intermediate tables would be left on the database; administrators could remove them using a database-side scheduled task. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. See the screenshot below:In the Select Configuration dialog, go to Project definition > Advanced. There are a number of them. Expand the Governing settings, then select Results Set Row Limit. 4. These VLDB properties control the method by which the report data are normalized. The Use default inherited value option indicates the level that is active, while the SQL preview box. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Dependent Object Options: Enable Find and Replace object dependencies: If the checkbox is selected, a user is allowed to find all dependent objects and replace them. Some databases do not support implicit creation, so this is a database-specific setting. Check for VLDB properties tuning to see if SQL generation is using standards or best practice as per DB that we use (like Intermediate Table Type) Check individual pass by pass to see where the problem is. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. Under Project-Level VLDB Settings, click Configure. Zillow has 471 homes for sale in Victoria BC. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. Both the SQL Date Format and. But the grid is not reset properly when adding and removing a derived element. Clicking in Preserve all pass the final elements option. You can determine the default options for each VLDB property for a database by performing the steps below. Property owners benefit from a fair number of nearby clothing stores. 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. As mentioned, these steps will need to be done for each report that sorting in this way is desired. The Database Connections dialog box opens. Choose one of the following: •. For this reason, two additional options are provided:Export to PDF: export a report or document to a PDF document: EXPORTTOPDF:. (The original name for this property, in fact, was "Incomplete lookup table. This article explains how to migrate VLDB Select propertyset from an older metadata to a newly created metadata. However, platform administrators can toggle this functionality if needed: In MicroStrategy Developer, platform administrator can select/deselect the Use parameterized queries checkbox under the Advanced tab of the Database Connections dialog. The dimensional model is included for backward compatibility with MicroStrategy 6. 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. 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 default syntax can be modified by using 'Column Pattern' VLDB property. To be effective. Here, we will use MicroStrategy Tutorial objects. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. 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. Some queries may benefit from distributing data by the fact columns as well as the attribute ID columns. 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. x and later). The solution is to backup old registry keys and re-generate default ones. Since these financial line item attributes include empty elements to support the hierarchical structure of the financial data, this causes some of the rows of the exported report to also be empty. The VLDB Properties Editor opens. In MicroStrategy 2020 Update 2, a new VLDB Property, Cartesian Join Governing, exists on the Project, Report, Dataset, and Visualization level. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. For steps, see the Upgrade Guide. The MDX cube report is executed. From here there will be a section for Analytical engine VLDB properties and an option to "Configure". 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. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. 203 Exercise 7. Alter VLDB Properties You will need to alter two properties: Additional final pass option and Apply filter options. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. 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. 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. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. This issue has been addressed starting in MicroStrategy 9. KB19860: What is the ‘Attribute Selection Option for Intermediate Pass’ VLDB property in MicroStrategy Developer 10. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Published: 4월 6, 2017. Right-click on an existing environment and choose Properties. Right-click on the report and click on the 'Edit' menu. x, select 'Project Documentation' from the Tools menu to. ; Click the General tab. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. You can determine the default options for each VLDB property for a database by performing the steps below. Open the Workstation window. For an Intelligent cube or incremental refresh report, right-click it and choose Edit. The XQuery Success Code VLDB property lets you validate Transaction Services reports that use XQuery. 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. If the size for a SQL pass. The Use default inherited value option indicates the level that is active, while the SQL preview box displays a description of the selected setting. Report designers can then view the messages immediately without accessing the Intelligence Server machine. Dashboard performance troubleshooting in MicroStrategy 10. txt) or read online for free. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. These values are set by default when the "Teradata 12" database object is used (set at Configuration Managers > Database Instances > Database Instance. When they do appear, report designers have some degree of control over the subquery syntax using the Very Large Data Base. To view VLDB properties. A given VLDB setting. x or earlier. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. In the Attribute Editor, on the Tools menu, select VLDB Properties. Total views 28. 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 final pass will perform two operations. 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. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. In this example, the raw ID is used. 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 is Microstartegy way of handling database specific preferences while generating the report SQL. Open navigation menu. 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. 1, the VLDB property ‘Analytical Engine > ‘Filtering on String Values’ has been available at project level. The upgrade database type window appears. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. Open the report template in the Template Editor. 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). This technical article explains expected new behavior in MicroStrategy 10. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. Description Understanding your data characters and choosing the matched. By default, they are defined by MicroStrategy, optimized for the database and its version. You must have the "Use VLDB property editor" privilege to make changes to the setting. For a data source, right-click it and choose Edit. Open your report in the Report Editor. 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. If this VLDB property is not displayed, you must upgrade the project metadata. For steps, see the MicroStrategy Developer help. This VLDB property is useful only for MDX cube reports that access an Oracle Hyperion Essbase MDX cube source. Open the VLDB Properties Editor this way. Select VLDB Properties from the Data menu. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Under the VLDB properties for the report, change the Additional Final Pass Option setting to One. 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. " In MicroStrategy SQL Generation Engine 8. Intermediate Table Type . In. For a project, right-click it and choose Advanced Properties. x and 10. The following diagram shows how VLDB properties that. Solutions available. . Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. A given VLDB setting can support or optimize one system setup, but the same setting can cause performance issues or errors for other systems. Metrics using count or average, metrics with dynamic aggregation. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. . See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. At the report level, change the. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. x. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. The image below shows how this hierarchy is populated on a report in. You can specify another. User changing own language. for more information on this setting. 1 includes a new VLDB property, Custom Group Display for Joint Elements'. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. Allow joins based on unrelated common. 2021 Update 7 (September 2022) MicroStrategy Workstation. The VLDB Properties (Report) dialog box opens. . Additional details about each property, including examples where necessary, are provided in the sections following the table. On the Advanced tab, select the Use parameterized queries check box. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. On the Advanced tab, select the Use parameterized queries check box. WHERE (col1, col2) in (SELECT s1. 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. 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. 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. You can configure this setting. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". for more information on this setting. VLDB. Under VLDB Settings, navigate to the desired VLDB option. Project. 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. The “#n” code in Apply function syntax serves as placeholders for the MicroStrategy objects being passed to your database. KB40199: "The tokens 'NTLINK' and 'IMPORTWINUSER' should not be used. . Certain VLDB properties use different default settings depending on which data source you are using. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. " Uncheck the "Use default inherited value" checkbox. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. VLDB (Very Large DataBase) properties allow you to customize the SQL that MicroStrategy generates. •. Since full outer joins can require a lot of database and Intelligence Server resources, and full outer joins are not supported for all databases, it. 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. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. By default, they are defined by MicroStrategy, optimized for the database and its version. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. Database instances for the project source are displayed. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. 4. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. See Template Editor. Join common attributes (reduced) on both sides. The last statement can contain multiple SQL statements concatenated by “;”. Be careful though, because these settings are applied set as the defaults for. 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 ). Micro Strategy Interview Questions and Answers - Free download as PDF File (. Choose Data > Report Data Options. Notice the new setting under Project Configuration > Project Definition > Advanced > Analytical engine VLDB properties > Subtotals over consolidations compatibility:In MicroStrategy 2020 Update 2, a new VLDB Property, Cartesian Join Governing, exists on the Project, Report, Dataset, and Visualization level. 4. It is recommended to always stay on the latest MicroStrategy release so you can always have the best Snowflake experience out of the box. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Clear the Use default inherited value check box. 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. Possible Values Default Values; Metrics Join Across Datasets: Determines how values for metrics are calculated when unrelated attributes, from different datasets of a dossier or document, are included with metrics. The VLDB properties at the different levels work together to affect report results. See the warning above if you are unsure about whether to set properties to the default. In the Metric Editor, on the Tools menu, point to Advanced Settings, and then select VLDB Properties. Both properties are located in the Query Optimizations folder in the VLDB property editor. See How to Edit VLDB Settings in. Check the SQL generated by MSTR is good (without cross joins) Check for the execution plan on database. STEPS TO REPRODUCE: In Web, create a report with the attributes Customer Region, Category,. VLDB properties are usually determined by an administrator, but some may also be defined by a project’s designer. 1) From the Data menu, access the VLDB Properties option. 39 Intermediate Table Type VLDB property. Doc Preview. View listing photos, review sales history, and use our detailed real estate filters to find the perfect place. Select either Disable or Enable depending on whether you want to disable or enable. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. Default VLDB properties are set according to the database type specified in the database instance. In the confirmation window that appears, click Yes. The options for this. A given VLDB setting can support or. 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 arrows depict the override authority of the levels, with the report level having the greatest authority. pdf - MicroStrategy. Beginning with MicroStrategy 9. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. You can check out the 3 options in VLDB Properties / Joins / From Clause Order While you are there, check out the last option under VLDB. This feature is similar to what we see in. Click Properties. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. "The table below summarizes the Joins VLDB properties. 4. Choose Tools > Show Advanced Settings option if it is. Viewing VLDB properties. Viewing and Changing VLDB Properties. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. Choose the database instance and then open VLDB Properties. In the VLDB Properties dialog, go to Analytical Engine > Data Engine Version. x. To identify attributes that include empty elements, type the ID value for each attribute in the text field for this VLDB property. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. NIT Rourkela. Sometimes pre-statement VLDB Properties are used to set database priority. Select the radio button labeled "Outer Join. 3. 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. Join common key on both sides. MDX cubes are also referred to as MDX cube sources. 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. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. There are number of them. 4. This article introduces a new VLDB property "Attribute Relationship Model" on Data Import Intelligent Cube dataset starting MicroStrategy 2021 Update 3 which allows Application Architect to quickly switch a Dataset from default "Attributes can be related through imported tables" mode to "Attributes can be related through 1:M relationships only" mode. Single SQL pass time-out in seconds. 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. ini file which is located at <Installation Path>Common FilesMicroStrategy (Windows platform) or <Installation Path>/MicroStrategy/install (Linux platform)An intermediate table is a table created on the database to store temporary data that are used to calculate the final result set. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. 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. 1 and 10. 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. MicroStrategy SQL Generation Engine 9. In MicroStrategy Developer, open a report in the Report Editor. . 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. Enter the desired location under 'Database name' in the 'Intermediate table storage' section. However, you want to show all the store. 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. If this is required by MicroStrategy Technical Support for trouble-shooting an issue, copy and paste the contents of this report into notepad and send it. Description. For information about accessing these properties, see. It is strongly encouraged that you post your questions on the community forum for any community based. Access the VLDB Properties Editor. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. Fact extensions may require subqueries, depending on their definition. 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. Possible locations for VLDB optimizations in the query structure are. 5 : If the Use default inherited value check box is selected, clear it. The option "SQL Global Optimization" under Query Optimizations is not available when a report VLDB properties need to be changed. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. x report for a specific attribute using an ApplySimple statement as one of its forms. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. MicroStrategy application developers can further optimize SQL for their specific Oracle environment using these string insertion settings. This controls whether the MDX function TopCount is used in place of Rank and Order to support features such as metric qualifications. The reports created from an intelligent cube do not have this VLDB property used in normal reports. Additional details about each property, including examples and a list of wild cards, are available by clicking on the links in the table.