Properties set at the report level override properties at every other level. This setting is called Join Across Datasets. 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. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. 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. 1. Additionally, the COALESCE function can be included in the SQL query. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. The following list summarizes the metric-specific VLDB properties that can be set at the metric level. Intermediate Table Type . MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. The table b elow summarizes the Query Optimizations VLDB properties. In MicroStrategy Developer, from the File menu, point to New, and select Transformation. Description Understanding your data characters and choosing the matched. 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. b. In MicroStrategy 10. Log in to a project in MicroStrategy Developer. From the Tools menu, select Create VLDB Settings Report. x has changed the default value of the "SQL Global Optimization" VLDB property. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. It is strongly encouraged that you post your questions on the community forum for any community based. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. This VLDB setting is located in the 'Indexing' folder and has the following options:MicroStrategy constantly optimizes the queries and sets new defaults for the VLDB properties so customers can take advantage of the best performance possible. This is reflected in the checkbox “Use default inherited value for all VLDB properties”. You can set additional metric VLDB properties at other levels, such as the report and project levels. 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. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB 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. 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. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. From the Data menu, choose VLDB Properties. The following. 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. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. x, the only options were to drop tables or do nothing. Expand the Database instances folder. Accessing Report VLDB Properties. You will study concepts such as level metrics, transformation. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. MicroStrategy TutorialPublic ObjectsReportsMicroStrategy Platform CapabilitiesAd hoc ReportingSortingYearly Sales!i inserts the. Diagnosis. - 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 an Intelligent cube or incremental refresh report, right-click it and choose Edit. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. The following settings are advanced properties which are. mstr) file size (MB) setting. In MicroStrategy Developer 9. If the report result set exceeds the limit specified in the Result Set Row Limit, the report execution is terminated. Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of levels in hierarchy * 10). select a11. Choose the database instance and then open VLDB Properties. KB440837: MSTR 10. The setting is applied. pdf > VLDB Settings > VLDB properties > Query Optimizations > Dimensionality Model. " In MicroStrategy SQL Generation Engine 8. 1 and 10. VLDB (Very Large DataBase) properties allow you to customize the SQL that MicroStrategy generates. In the Results Set Row Limit field, type the limit. 4. 4. These settings affect how MicroStrategy Intelligence Server. This article explains the behavior of the commit level VLDB propertyThe MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. See Details for All VLDB Properties for more information. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. 4. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. ca. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. . Click the "VLDB Properties. Zillow has 471 homes for sale in Victoria BC. In MicroStrategy it is possible to generate outer joins between metrics at different levels, but there was the possibility of report results that could vary in ways outside the user's control if a straight outer join was performed. In the Report Editor click on 'Data'> 'VLDB Properties' option, as illustrated below. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. (For information on object levels, see Order of Precedence . MicroStrategy's Multisource option works by inserting the data into a temp table on the warehouse side, so you'd be right back where you started!A better solution if you don't like temp tables is to change the. This technical article explains expected new behavior in MicroStrategy 10. txt) or read online for free. The default syntax can be modified by using 'Column Pattern' VLDB property. 1, this property was known as Final Pass Result Table Outer Join to Lookup Table. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. For a project, right-click it and choose Advanced Properties. The options for this. (For information on object. For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. 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. Contact MicroStrategy. 5. Choose Tools > Show Advanced Settings option if it is. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. This article covers the purpose of the where clause driving table property. Parallel Query Execution is an advanced property that is hidden by default. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. •[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. Check the option according to the database used. It is recommended to always enable secure text input. 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. 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. Click the "VLDB Properties. Modify the VLDB property you want to change. Close suggestions Search Search. This section focuses on the VLDB properties that are set at the metric and report level. You can use this setting on the following levels: Project level; Report level; Dossier visualization levelWhy MicroStrategy Why MicroStrategy; Customer Stories; Platform45+ [REAL-TIME] MicroStrategy Interview Questions & Answers - Free download as PDF File (. Also, the Project level settings contain the Analytical Engine-related VLDB properties and the MDX VLDB properties. The new setting is a Database Instance level VLDB property called Default Sort Behavior for Attribute. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform Products; MicroStrategy ONE; AI & Augmented; Dossier; Library; Workstation; HyperIntelligence; Multi-Cloud; Embedded Analytics; Innovations; Futures. 4. The recommended VLDB optimizations for Teradata 12. Sub Query Type - VLDB setting that determines the SQL syntax of sub-queries for the database; Relationship filter - filters an attribute based on their relationship to other attributes; Steps to Reproduce. 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. Expand the 'Governing' folder and select 'SQL Time Out (Per Pass). See Details for All VLDB Properties for more information. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. 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. KB441418: Supplemental reference for installing Hotfix on MicroStrategy version 10. 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. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Character. Click VLDB Properties. The following example demonstrates the use of the VLDB property "Compute Non-Agg before/after OLAP functions (e. Click the Load button. The four attribute join types available in the Report Data Options dialog box are the same as those in the VLDB Properties dialog box. In the VLDB Properties window, expand the folder called. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. You can manipulate things like SQL join types, SQL inserts,. 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. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. 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. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. MicroStrategy Library. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. To create a last year transformation based on an expression. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. 3. Choose Tools > Show Advanced Settings option if it is not already selected. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. Export a Report Services document to Excel with formatting using URL API in MSTR Web. Viewing VLDB properties. 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. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Execute the report and view the SQL:September 06, 2018. However, each database instance is allowed to have its own VLDB property values. Certain VLDB properties use different default settings depending on which data source you are using. You can determine the default options for each VLDB property for a database by performing the steps below. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. The report SQL shows that the first metric is calculated at the level of Quarter (report. The dimensional model is included for backward compatibility with MicroStrategy 6. The full set of VLDB properties is documented in the MicroStrategy System Administration Guide. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. Allows the MicroStrategy SQL Engine to use a new algorithm for evaluating whether or not a Cartesian join is necessary. MicroStrategy Library Mobile iOS. Be careful though, because these settings are applied set as the defaults for. The Microstrategy SQL that has been generated can be customized using the VLDB properties. 4. In Developer: Go to Tools > Developer Preferences. MicroStrategy online help and PDF manuals (available both online and in printed format) use standards to help you identify. Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. For steps, see the Upgrade Guide. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Expand the Governing settings, then select Results Set Row Limit. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. Choose Tools > VLDB Properties. The Database Connections dialog box opens. List Parent User Groups. . For users with environments and metadata updated to MicroStrategy 2020, the Analytical Engine will ignore null values for aggregation functions in new projects by default. A given VLDB setting can support or optimize one system setup, but the same setting can cause performance issues or errors for other systems. Description. Since MicroStrategy Analytical Engine 9. Open the Workstation window. The Use default inherited value option indicates the level that is active, while the SQL preview box. Go to Database instances > SQL Data Warehouses. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. The VLDB Properties Editor opens. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Report Caching Options, available to users with. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Base Table Join for Template. x. From the Tools menu, select Set all values to default. How to change the syntax is described in detail by using examples. The properties are saved in different folders, as indicated in the previous list. 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 ). 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. 39 Intermediate Table Type VLDB property. 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. The two possible values are as. The Project Configuration Editor opens. Use the temp table prefix in the (Very Large Database) VLDB properties window. The default option is for aggregation calculations to ignore nulls and for scalar calculations to treat null values as zero. Cross joins are seen in metrics when joining across unrelated attributes inside of data blending. In MicroStrategy Developer, log in to a project. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. See Template Editor. 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. The VLDB Properties Editor opens. The Dimensionality Model property is strictly for backward compatibility with MicroStrategy 6. pdf), Text File (. You will study concepts such as level metrics, transformation. Clear the Use default inherited value check box. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the (missing or bad snippet) for steps to set this VLDB property. 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. a. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. 0 and higher). 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. Select either Disable or Enable depending on whether you want to disable or enable. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Restart MicroStrategy Intelligence Server (or, in a two-tier connection, disconnect and reconnect to the project source). 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. The VLDB Properties Editor opens. In an Intelligent Cube report, only the "Data Population for Intelligent Cubes" will be visible; in standard reports, it will be "Data Population for Reports. Upgrading Your Database Type Properties. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". 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. !o inserts the report name (can be used in all Pre/Post statements). The Grouping panel is displayed. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. This guide discussesBy selecting this option, the Join Type VLDB property is assumed to be Join 92 and any other setting in Join Type is ignored. These settings are passed to the specific report/job VLDB properties only from the project primary database instance. Under Categories, expand Calculations, and select Attribute Join Type. Victoria is a good city to buy a house in for those who prefer a slower-paced atmosphere. You can use this setting on the following levels: To edit the setting, you must have "Use VLDB property editor. The table b elow summarizes the Export Engine VLDB properties. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. DATA ANALYSIS. Right-click on an existing environment and choose Properties. •. The MDX cube report is executed. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. In the Project-Level VLDB settings area, click Configure. These settings are available only if the drill path destination is a template. 2. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". The "Evaluation Ordering" VLDB setting has two possible values, "6. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. 192 Determining the level to apply a VLDB property. 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. This information is available for each property in the VLDB Properties dialog box at each level. For information about accessing these properties, see. View full document. Any projects that existed prior to upgrading metadata to. This occurs when the data type of the attribute is timestamp. In the Data Engine Version field, view and modify the Data Engine version. By default, they are defined by MicroStrategy, optimized for the database and its version. Web Professional privileges. Open the report template in the Template Editor. . The VLDB properties are grouped into different property sets, depending on their functionality: Viewing and Changing VLDB Properties. Doc Preview. If the size for a SQL pass. Any existing projects will retain the null checking behavior that was. The Year - Define a new member attribute. It also displays all current settings for each VLDB property. For more details, go to Start -> Programs -> MicroStrategy -> Product Manuals -> Advanced Reporting Guide (PDF) -> 13. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. 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. 1. If this VLDB property is not displayed, you must upgrade the project metadata. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. Clear the Use default inherited value check box. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHyperIntelligence and its Architecture. 4. This property overrides the Number of report result rows. 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. This article documents an issue observed in MicroStrategy 2019, where the session ID parameter is not correctly set when using wildcards. VLDB properties can provide support for unique configurations. 3. The Project Configuration Editor opens. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. 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. The Use default inherited value option indicates the level that is active, while the SQL preview box displays a description of the selected setting. The maximum number of rows returned to the Server for the final result set. Property Type. Level dimensionality in a metric interacts differently with different features such as view filters, report filters, other metrics and certain VLDB properties. Parallel Query Execution is an advanced property that is hidden by default. 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. PDS file. 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. 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 Database Connections dialog box opens. The following settings are advanced properties which are. These properties apply only to MDX cube reports using data from an MDX cube. Open MicroStrategy Developer. It sets the general standards. For steps, see the MicroStrategy Developer help. Open the VLDB Properties Editor this way. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Expand the 'Administration' Icon, and select the Database Instance Manager. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. (0 = unlimited number of rows; -1 = use value from higher level. Metrics using count or average, metrics with dynamic aggregation. x. Topics Introduction to the MicroStrategy engine Basic optimizations Templates Metrics Filters The. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. To specify this setting, edit the VLDB properties for the database instance or for a report, expand Governing settings, then select the SQL Time Out (Per Pass) option. 1 and 10. Any projects that existed prior to upgrading metadata to MicroStrategy 2020 retain their original VLDB property settings. MicroStrategy Transaction Services and XQuery allow you to access. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. This is Microstartegy way of handling database specific preferences while generating the report SQL. Deliveries privileges. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. Instead, it creates two passes of SQL and creates all SQL correctly except without an outer join to the lookup table in the final pass. Report Level: Data -> VLDB Properties Unhide Parallel Options: Tools -> Show Advanced Settings Other VLDB settings that affect query generation. 1 and 10. MicroStrategy SQL Generation Engine 9. Set the additional final pass property to force an additional pass of SQL. The recommended VLDB optimizations for Oracle 11g are listed below. If you perform this procedure, any changes you may have made to any or all VLDB properties displayed in the chosen view of the VLDB Properties Editor will be. 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. In the left pane, click Advanced Properties. The VLDB Properties Editor opens. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. All entries follow a set format as noted below. The solution is to backup old registry keys and re-generate default ones. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. MDX cubes are also referred to as MDX cube sources. ; Click the General tab. Additional details about each property, including examples where necessary, are provided in the sections following the table. Property owners benefit from a fair number of nearby clothing stores. Loading × Sorry to interruptPlaces to Set VLDB Properties. 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. In MicroStrategy Developer, open a report in the Report Editor. 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. Find 513 houses for sale in Victoria, BC. MicroStrategy Office privileges. On the Advanced tab, select the Use parameterized queries check box. Dimensionality Model is an advanced property that is hidden by default. Preview Feature: The FreeForm SQL Report Editor allows you to write your own queries to create reports. This controls whether the MDX function TopCount is used in place of Rank and Order to support features such as metric qualifications. They are exactly the same. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. WHERE (col1, col2) in (SELECT s1. From the Data menu, select VLDB Properties. Additional details about each property, including examples where necessary, are provided in the sections following the table. User changing own language. To the right of the Database connection area, click Modify. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. Click on the upgrade button. Select Teradata V2R4 and move it to the right using the > button. Use this section to learn about the VLDB properties before modifying any default settings.