On MicroStrategy Web and Workstation, the same. This VLDB setting can be changed at the Database instance, Report, and Metric levels. 1 includes a new VLDB property, Custom Group Display for Joint Elements'. Fact Tables 2. Multiple passes are generated only when necessary to resolve all the metric definitions. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. en Change Language. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. pdf - MicroStrategy. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. In the confirmation window that appears, click Yes. Click Save and Close. 15. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. 3. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. For example, if a VLDB property is set one way for a report and the same property is set differently for the database instance, the report setting takes precedence. Metrics using count or average, metrics with dynamic aggregation. It is strongly encouraged that you post your questions on the community forum for any community based. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Go to Database instances > SQL Data Warehouses. Group by alias. Also, the Project level settings contain the Analytical Engine-related VLDB properties and the MDX VLDB properties. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Export to exports the report to Microsoft Excel, Microsoft Word, Microsoft Access, a text file, an HTML file, or a PDF file. In MicroStrategy Developer, open a report in the Report Editor. Base Table Join for Template. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". 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. Below are the list of parameters that the URL must. Clicking in Preserve all pass the final elements option. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. 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. The table b elow summarizes the Pre/Post Statements VLDB properties. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. 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. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. Certain VLDB properties exist at the database instance level but are viewed by the SQL Engine as unrelated to the database used. Visit REALTOR. 4. Upgrading Your Database Type Properties. 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. The recommended VLDB optimizations for Oracle 11g are listed below. 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. Order of Precedence. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. KB40199: "The tokens 'NTLINK' and 'IMPORTWINUSER' should not be used. 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. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. x. In MicroStrategy 7. In the VLDB Properties dialog, go to Analytical Engine > Data Engine Version. The upgrade database type window appears. 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. 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). 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. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. mstrc) Open Workstation. In our current design, report pre/post statement 5 is different from 1-4. It has the following five options:What are VLDB properties? VLDB stands for Verly Large Data Base Properties. To modify the String Comparison Behavior VLDB property for an attribute. The attribute level follows a consecutive order from. The Database Instances Editor opens. Accessing and Working with VLDB Properties. The VLDB Properties Editor opens. 3. If you choose Temp Table Join. How to change the syntax is described in detail by using examples. 8 From the File menu, click Save As. See the warning above if you are unsure about whether to set properties to the default. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. In MicroStrategy 10. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. Remove the training metric from the report. From the Tools menu, select Grouping. Different scenarios will be explored throughout this article to better understand the logic of how MicroStrategy is working. It is recommended to always enable secure text input. 1, the VLDB property ‘Analytical Engine > ‘Filtering on String Values’ has been available at project level. 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. Expand the Database instances folder. 3. Under Project-Level VLDB Settings, click Configure. The most basic DBMS (database) level where properties are defined. 1. Open the report template in the Template Editor. 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 reads the settings from the updated DATABASE. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. 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. 1, this property was known as Final Pass Result Table Outer Join to Lookup Table. But the grid is not reset properly when adding and removing a derived element. . Parallel Query Execution. Clear the Use default inherited value check box. Locate the desired property. The following. Maximum SQL Size (Database Instance) You can limit the size (in bytes) of the SQL statement per pass before it is submitted to the data warehouse. 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. . Enter the desired location under 'Database name' in the 'Intermediate table storage' section. 4. •Students review the most commonly used VLDB properties in certain categories, such as indexing, joins, pre/post statements, query optimizations, and tables. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. The attribute uses a CASE statement to replace NULL values with -999. Admin. This article covers the purpose of the where clause driving table property. Doing so, we. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategyMicroStrategyEnginesAndSQL 11 2 1. The Project Configuration Editor opens. This article explains how to migrate VLDB Select propertyset from an older metadata to a newly created metadata. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. . The Database instances - SQL Data warehouses pane displays. To access the setting, in MicroStrategy Developer right-click on the project and select Project Configuration…Then, In the Project Configuration dialog box, choose Project Definition >. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. x. You can determine the default options for each VLDB property for a database by performing the steps below. 5 From the Data menu, select VLDB Properties. For more information regarding post statements defined at the report level, refer to the following Technical Note:There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. 0. The VLDB properties at the different levels work together to affect report results. MicroStrategy added an Advanced Properties dialog that includes elements formerly know as VLDB properties, as well as other items including report data properties such as Evaluation Order. For a project, right-click it and choose Advanced Properties. The setting is applied. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. pdf), Text File (. The maximum number of rows returned to the Server for the final result set. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. The "Evaluation Ordering" VLDB setting has two possible values, "6. A given VLDB setting can support or optimize one system setup, but the same setting can cause performance issues or errors for other systems. 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 ). You can configure this setting. . This section tells you how to do the following: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. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. Accessing Report VLDB Properties. 6 :Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. x or earlier. This setting affects all the metrics in this project, unless it is overridden at a lower level. For information about accessing these properties, see. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Group by position. The resulting report in the 'VLDB Settings Report' dialog box represents a list of non-default VLDB properties that have been enabled for that report. Click Save and Close to save your changes. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Be careful though, because these settings are applied set as the defaults for. For steps, see the Upgrade Guide. The property "RowGoverning4CostlyFunctions" is a hidden limit that was introduced in MicroStrategy to prevent memory issues or crashes when many complex metrics are used at the same time. See the Advanced Reporting Guide. The final pass will perform two operations. Web Analyst privileges. 4. Under VLDB Settings, navigate to the desired VLDB option. 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. Dimensionality Model. Modify the VLDB property you want to change. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. It also displays all current settings for each VLDB property. By default, all properties are governed by the one at the top level. To Configure a Report for Bulk Export. col2…) While the default values should result in the. Allows the MicroStrategy SQL Engine to use a new algorithm for evaluating whether or not a Cartesian join is necessary. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. In this example, the raw ID is used. The MicroStrategy SQL Generation Engine provides a Very Large Database (VLDB) property Called “GROUP BY Non-ID Attribute. The XQuery Success Code VLDB property lets you validate Transaction Services reports that use XQuery. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Each queue is defined by concurrency level, user groups, query groups, wild cards, memory percent to be used,. However, you want to show all the store. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Open your report in the Report Editor. <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. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. This syntax can be costly for most Relational Database Management System (RDBMS) platforms when the fact tables involved are large in size. They are exactly the same. b. 1 and 10. Throughout the course, students gain hands-on practice via a series of exercises. WHERE (col1, col2) in (SELECT s1. You can specify another. Some databases do not support implicit creation, so this is a database-specific setting. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. The VLDB Properties Editor opens. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. In the Report Editor click on 'Data'> 'VLDB Properties' option, as illustrated below. 203 Exercise 7. From the Data menu, choose VLDB Properties. 1, this can be done at the report level by following the steps in technical note 10073. 3) Explain how intelligent cubes are different from ordinary cubes?. 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. It is very. 3. The system reads them from the same location. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to fa. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. When a Database Instance is configured to use the “Azure SQL Data Warehouse” database connection type, the recommended values for all VLDB properties will automatically be. 4. For example, you can choose to apply a setting to an entire database instance or only to a single report associated with that database instance. For use cases, examples, sample code, and other information on every VLDB property. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. At the bottom of the Options and Parameters area for that. In Developer, right-click the report to set the limit for and select Edit. (For information on object. VLDB properties can provide support for unique configurations. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. Database Instance. The following settings are advanced properties which are. A possible business case that could be solved by this approach: A large fact table that summary reports are sourcing, from which it is necessary to drill down through a report (or report template) to row level data. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results. The reports created from an intelligent cube do not have this VLDB property used in normal reports. To set these properties, right-click a project within the database instance to be updated. Other VLDB Properties are mentioned below. A given VLDB setting can support or. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. Preview Feature: Create and edit reports with your favorite features including the Advanced Properties panel, View Filters, SQL View, and many more. In statement 5:An example is shown with MicroStrategy Tutorial Project: - In Microstrategy Developer, log into the project where it is desired to obtain a report's VLDB properties. 1 and 10. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. 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. Change the VLDB setting . Double-click Time to open the folder, then double-click Year. For a detailed explanation of how to support financial reporting in MicroStrategy, along with using this VLDB property to identify attributes that include empty elements, refer to the Project Design Help. Zillow has 471 homes for sale in Victoria BC. In the confirmation window that appears, click Yes. 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 ). Use Case Statement option available in VLDB Properties, If your report contains any Custom Groups. Database Instance > VLDB Properties Report Level: Data > VLDB. Character. View full document. XQuery Success Code is an advanced property that is hidden by default. "The table below summarizes the Joins VLDB properties. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. DeanElectronHummingbird14. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. Non-aggregatable metrics are defined in MicroStrategy using the metric dimensionality Grouping = Beginning or Ending (fact. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". 2. x, "Use relational model" is selected by default. Subqueries (or correlated subqueries) are used infrequently but significantly in the MicroStrategy SQL Generation Engine. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy In MicroStrategy SQL Generation Engine, a VLDB (Very Large Data Base) property "Set Operator Optimization" provides the option to use database-side set operators to combine intermediate results sets representing set qualifications in filters. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. 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. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. This is reflected in the checkbox “Use default inherited value for all VLDB properties”. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. A few common ones are for Attribute or Metric join types, cross join check, type of intermediate table, etc. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. The most basic DBMS (database) level where properties are defined. 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. 10 Snowflake Derived Tables require non-standard Outer Join VLDB property settings. If a table has been imported from only one database instance, the secondary database instance panel will be empty and disabled. This information is available for each property in the VLDB Properties dialog box at each level. . The Parallel Query Execution is an advanced property which determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. Based on these VLDB (Very Large Data Base), the Intelligence server manages the query optimization, calculations, and metrics. x still supports third-party gateway solutions. This setting is called Join Across Datasets. 2) In Joins, select Preserve all the final pass result elements. 1. VLDB properties cannot be modified from MicroStrategy Web. The Database Instances Editor opens. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. A given VLDB setting. 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. From the Data menu, select VLDB Properties. In the VLDB Properties window, expand the folder called. 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. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. The recommended VLDB optimizations for Oracle 11g are listed below. VLDB properties also help you configure and optimize your system. x, select 'Project Documentation' from the Tools menu to start the wizard. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. The fact columns can also be included in the primary index, using the Allow index on metric VLDB property. To the right of the Database connection area, click Modify. Pages 100+ Identified Q&As 2. 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. pdf > VLDB Settings > VLDB properties > Query Optimizations > Dimensionality Model. 5. 201 Modifying VLDB properties at the report level. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. The VLDB property's behavior will be demonstrated using the following attribute and report. The table b elow summarizes the Export Engine VLDB properties. Some queries may benefit from distributing data by the fact columns as well as the attribute ID columns. The Project Configuration Editor opens. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. Database instances for the project source are displayed. 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). A given VLDB setting can support or. Both the SQL Date Format and. The attribute opens in the Attribute Editor. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. . Restart the Intelligence server to apply the changes. The following example demonstrates the use of the VLDB property "Compute Non-Agg before/after OLAP functions (e. 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. For new installations of MicroStrategy 8. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. Victoria's peaceful atmosphere and vibrant real estate market make it a great place to search for your next home. Follow the steps below to change the property. Community & Support Search Discussions Open A Case View My Cases1. This section focuses on the VLDB properties that are set at the metric and report level. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the. The "Evaluation Ordering" VLDB setting affects the order in which the Analytical Engine will perform various calculations. Specifying the Display Mode and VLDB Properties. x, the only options were to drop tables or do nothing. This Knowledge Base article describes how using Snowflake data base outer joins are automatically set as off/ (nosupport) SYMPTOM. MicroStrategy Office privileges. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Open the database instance for the project. This VLDB property is useful only for MDX cube reports that access an Oracle Hyperion Essbase MDX cube source. 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. Open MicroStrategy Developer. This setting is useful if you have only a few attributes that require different join types. 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. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. Then set the apply filter options property to. MicroStrategy Transaction Services and XQuery allow you to access. 4. This setting is used as an optimization for some databases which perform better when columns coming. 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. This article describes the best practices to be taken when connecting an instance of Azure Synapse Analytics in MicroStrategy. Go to Metrics > NULL Check. Choose Data > Report Data Options. even when the "Inherit VLDB" is set to false in the drill map. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. 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. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. mstr) files that can be sent through Distribution Services is defined by the MicroStrategy (. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. If the report result set exceeds the limit specified in the Result Set Row Limit, the report execution is terminated. MicroStrategy Library Mobile iOS. Properties set at the report level override properties at every other level. In. Navigate to 'Pre/Post Statements' and 'Report Pre Statement 1. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. A given VLDB setting can support or. •The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. . This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. The four attribute join types available in the Report Data Options dialog box are the same as those in the VLDB Properties dialog box. 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. Property Type. In MicroStrategy, there is a Very Large Data Base (VLDB) property, "Additional Final Pass Option," that configures whether or not the engine will optimize SQL into a single pass when possible. There are number of them. - On MicroStrategy Developer main toolbar, cick on ToolsProject Documentation - Follow the wizard selecting: (1) Application Objects (2) Advanced DefinitionIt is found in the Analytical Engine folder of the VLDB Properties (Metric) dialog box, pictured below. For a project, right-click it and choose Advanced Properties. From the Project Configuration screen, choose Database Instances, select the Database Instance you want to configure, and click VLDB Properties. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of levels in hierarchy * 10). Report Caching Options, available to users with. MDX cubes are also referred to as MDX cube sources. MicroStrategy Advanced Reporting Guide provides comprehensive information on advanced topics for using the MicroStrategy query and reporting. In MicroStrategy Developer, open a report in the Report Editor. Additional details about each property, including examples where necessary, are available by clicking on the links in the table. Preserve Common Elements of Lookup and Final Pass Result Table (Default). This property is report-specific. MicroStrategy Engine Components 27 MicroStrategy supported database platforms 276 MovingAverage function 255 Multipass SQL 37 N Nested Metrics 160 Non-Aggregatable metrics 142 O Oracle 292, 299, 304, 318, 327, 328, 329 Output level 193 P Partitioning 330 Permanent table 330 Permanent Tables 326 Pre/Post Statements 299 wildcards 301. The Grouping Properties dialog box opens. MicroStrategy TutorialPublic ObjectsReportsMicroStrategy Platform CapabilitiesAd hoc ReportingSortingYearly Sales!i inserts the. The recommended VLDB optimizations for Teradata 12. 1: Creating a report with missing aggregated values. 1 and 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. Select VLDB Properties from the Data menu.