For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. 0, a VLDB property is available to control. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. This article covers the purpose of the where clause driving table property. There are a number of them. Disable parallel query execution (default): All queries for MicroStrategy reports and Intelligent Cubes are processed sequentially. See Template Editor. OR. 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. XQuery Success Code is an advanced property that is hidden by default. Open the report template in the Template Editor. Additional VLDB Settings. You can specify another. Scribd is the world's largest social reading and publishing site. Changes made to this VLDB setting can cause differences to appear in your data output. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. This issue has been addressed starting in MicroStrategy 9. Accessing Report VLDB Properties. 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. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. Number of Views 948. Each queue is defined by concurrency level, user groups, query groups, wild cards, memory percent to be used,. This article explains the behavior of the commit level VLDB propertyThe post-execution SQL that was available in Narrowcast can be replaced by implementing post-report SQL VLDB properties. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. By default, they are defined by MicroStrategy, optimized for the database and its version. This information is available for each property in the VLDB Properties dialog box at each level. 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. This property is report-specific. This article covers the purpose of the where clause driving table property. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. To the right of the Database connection area, click Modify. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. These properties apply only to MDX cube reports using data from an MDX cube. Solutions available. 4. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. MicroStrategy Transaction Services and XQuery allow you to access. 1. 5. To set these properties, open the report in the Report Editor or Report Viewer. Level dimensionality in a metric interacts differently with different features such as view filters, report filters, other metrics and certain VLDB properties. Hierarchy 2: 4. x, the only options were to drop tables or do nothing. Micro Strategy Interview Questions and Answers - Free download as PDF File (. 4. The default option is for aggregation calculations to ignore nulls and for scalar calculations to treat null values as zero. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. The 'Attribute Selection Option for Intermediate Pass' VLDB property allows the user to choose whether to select additional attributes (usually these parent attributes) needed on the template as the join tree and. Order of Precedence. Beginning with MicroStrategy SQL Engine 9. The Data population for Intelligent Cubes VLDB property allows you to define if and how Intelligent Cube data is normalized to save memory resources. 3. In the latter case, intermediate tables would be left on the database; administrators could remove them using a database-side scheduled task. 4. 2. This article describes best practices to be taken when connecting an instance of PostgreSQL in MicroStrategy. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. Click VLDB Properties. The Grouping panel is displayed. Open the Workstation window. These settings affect how MicroStrategy Intelligence Server. x. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. Attribute. Possible locations for VLDB optimizations in the query structure are. Other VLDB Properties are mentioned below. 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. The VLDB Properties Editor opens. Follow the steps below to change the property. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. You can specify another. Also, the Project level settings contain the Analytical Engine-related VLDB properties and the MDX VLDB properties. Any projects that existed prior to upgrading metadata to. What ensures that object definitions are kept consistent and accurate across all environments when objects are migrated from a testing environment to a production environment You answered: Migration manager Incorrect Correct. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. The maximum file size of dashboard (. 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 ). Click Save and Close. When a report that includes these financial line item attributes is exported to Excel or as a PDF using MicroStrategy Web, all rows of data are exported. In MicroStrategy Developer, open a report in the Report Editor. Here, we will use MicroStrategy Tutorial objects. In the Attribute Editor, on the Tools menu, select VLDB Properties. Use VLDB property editor: use the VLDB Properties Editor: USEVLDBEDITOR: View ETL information:. 8/7/2021. 5. 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. Certain VLDB properties use different default settings depending on which data source you are using. Workstation is a unified tool that brings the power of administration and design together for the individual business user. Find 513 houses for sale in Victoria, BC. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. Click the Load button. These settings are available only if the drill path destination is a template. 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. In order to export a document in excel format using the URL API, the executionMode must be set to 4. 4. In MicroStrategy Developer, browse to an attribute, then right-click the attribute and select Edit. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to fa. In the VLDB Editor open the 'Tables' folder and click on 'Intermediate Table Type. ; By default, the Bulk export database instance, which is the database instance for the database containing the report data, is defined as the data warehouse for the project. 2. Additional details about each property, including examples and a list of wild cards, are available by clicking on the links in the table. This section focuses on the VLDB properties that are set at the metric and report level. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. The four attribute join types available in the Report Data Options dialog box are the same as those in the VLDB Properties dialog box. Allow joins based on unrelated common. Modify the VLDB property you want to change. 3. The VLDB Properties Editor opens. If a message saying that the type already exists, click on Yes to update it. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. The VLDB Properties Editor opens. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategyMicroStrategyEnginesAndSQL 11 2 1. col2…) While the default values should result in the. (0 = unlimited number of rows; -1 = use value from higher level. From here there will be a section for Analytical engine VLDB properties and an option to "Configure". By default, they are defined by MicroStrategy, optimized for the database and its version. 2: Modifying join. These values are set by default when the "Teradata 12" database object is used (set at Configuration Managers > Database Instances > Database Instance. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. This reads the settings from the updated DATABASE. Preserve Common Elements of Lookup and Final Pass Result Table (Default). In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. The following settings are advanced properties which are. Some databases do not support implicit creation, so this is a database-specific setting. Both the SQL Date Format and. Upgrading Your Database Type Properties. Open the VLDB Properties Editor this way. Select VLDB Properties from the Data menu. 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. The most basic DBMS (database) level where properties are defined. NIT Rourkela. ")This is a known issue prior to MicroStrategy SQL Engine 9. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. 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. The "Evaluation Ordering" VLDB setting has two possible values, "6. . 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. In MicroStrategy Developer, choose File > New > Report. select a11. Group by position. 1, this property was known as Final Pass Result Table Outer Join to Lookup Table. This setting is used as an optimization for some databases which perform better when columns coming. The most basic DBMS (database) level where properties are defined. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. 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. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform Products; MicroStrategy ONE; AI & Augmented; Dossier; Library; Workstation; HyperIntelligence; Multi-Cloud; Embedded Analytics; Innovations; Futures. To View and Change VLDB Properties Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. On the Freeform Sources tab, select Create Freeform SQL report. For a project, right-click it and choose Advanced Properties. 4. Go to Metrics > NULL Check. Restart the Intelligence server to apply the changes. You can choose to have the report display or hide the information described above, by selecting. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. In MicroStrategy 2020 Update 2, a new VLDB Property, Cartesian Join Governing, exists on the Project, Report, Dataset, and Visualization level. See Details for All VLDB Properties for more information. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. VLDB properties allow you to customize the SQL that MicroStrategy generates. Database instances for the project source are displayed. If excutionMode is not provided in the URL, by default PDF will be used as executionMode. The VLDB Properties (Report) dialog box opens. 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. b. 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. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. It is strongly encouraged that you post your questions on the community forum for any community. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. " Uncheck the "Use default inherited value" checkbox. This setting affects all the metrics in this project, unless it is overridden at a lower level. Lookup Tables VLDB Settings provide minimal modifications to this order. 3. 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. . The fact columns can also be included in the primary index, using the Allow index on metric VLDB property. Lets you identify attributes that include empty elements, which can then be ignored when. 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 headings to view a summary of the properties listed for that folder. 3. Dimensionality Model is an advanced property that is hidden by default. Click on the upgrade button. 4. 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. 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. 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. col2…) While the default values should result in the. Export to PDF filter summaries include the full attribute and metric names. If the size for a SQL pass. 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). To remove the COALESCE function from the SQL generated by the MicroStrategy SQL Engine, perform one of the following actions: At the project level, change the VLDB property 'Full Outer Join Support' to 'No support' from the Database Instance's VLDB properties under the 'Joins' group. Default VLDB properties are set according to the database type specified in the database instance. (This exception case is supported in MicroStrategy 2020 Update 5 and above, MicroStrategy 2021. This article describes what the evaluation ordering property is in MicroStrategy 9. The Results Set Row Limit VLDB property is used to limit the number of rows returned from the final results set SELECT statements issued. VLDB (Very Large DataBase) properties allow you to customize the SQL that MicroStrategy generates. Report designers can then view the messages immediately without accessing the Intelligence Server machine. The table b elow summarizes the Export Engine VLDB properties. Accessing Database Instance VLDB Properties. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. Right-click on the report and click on the 'Edit' menu. 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. 2. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. KB19860: What is the ‘Attribute Selection Option for Intermediate Pass’ VLDB property in MicroStrategy Developer 10. The following example demonstrates the use of the VLDB property "Compute Non-Agg before/after OLAP functions (e. 1 and 10. Parallel Query Execution is an advanced property that is hidden by default. Victoria is a good city to buy a house in for those who prefer a slower-paced atmosphere. QUARTER_ID QUARTER_ID, KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. The VLDB properties at the different levels work together to affect report results. •. Choose Data > Configure Bulk Export. This is Microstartegy way of handling database specific preferences while generating the report SQL. Join common attributes (reduced) on both sides. VLDB properties cannot be modified from MicroStrategy Web. By default, all properties are governed by the one at the top level. This setting is called Join Across Datasets. Open your report in the Report Editor. Export a Report Services document to Excel with formatting using URL API in MSTR Web. When using a Snowflake database it may appear that the Metric Outer join option is turned on. You can set additional metric VLDB properties at other levels, such as the report and project levels. The MicroStrategy Tutorial project uses aggregate tables by default. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. 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. For information about accessing these properties, see the page reference for each property in the table below. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. Total views 28. Select the radio button labeled "Outer Join. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. One way to implement multi-pass SQL is to execute each pass (each query block) in a separate table. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. Clear the Use default inherited value check box. List all parent groups of a user group 'sGroup'. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". The Microstrategy SQL that has been generated can be customized using the VLDB properties. Beginning with MicroStrategy 9. . Clear the Use default inherited value check box. Open MicroStrategy Developer. x introduces a third option to the VLDB Property "Drop Temp Table Method. x, select 'Project Documentation' from the Tools menu to start the wizard. 2021 Update 7 (September 2022) MicroStrategy Workstation. The dimensional model is included for backward compatibility with MicroStrategy 6. 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. Preview Feature: Create and edit reports with your favorite features including the Advanced Properties panel, View Filters, SQL View, and many more. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. Clicking in Preserve all pass the final elements option. Very Large Database (VLDB) properties are settings in charge of performing database specific optimizations (customizing Structured Query Language (SQL)). MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. The Preserve all lookup table elements. x. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. Sometimes pre-statement VLDB Properties are used to set database priority. Then go to the key “Query Optimization” > “Data Population for Intelligent Cubes” and choose the optimal option. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. 1 and 10. Possible locations for VLDB optimizations in the query structure are. VLDB properties can provide support for unique configurations. . Single SQL pass time-out in seconds. 4. x, outer joins are designed to get all the data from the lookup tables. A given VLDB setting can support or. Preview Feature: A new data. Select either Disable or Enable depending on whether you want to disable or enable. Accessing and Working with VLDB Properties. 7 Click Save and Close in the VLDB Properties Editor. The image below shows how this hierarchy is populated on a report in. See Template Editor. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. MicroStrategy Transaction Services and XQuery allow you to access. 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. Expand the Governing settings, then select Results Set Row Limit. Choose Tools > Show Advanced Settings option if it is not already selected. The report SQL shows that the first metric is calculated at the level of Quarter (report. For new installations of MicroStrategy 8. For information on connecting to databases, see Connect to Databases. Local temporary tables, indicated with the "#" character, are stored in tempdb and incur less overhead. You can determine the default options for each VLDB property for a database by performing the steps below. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Accessing Report VLDB Properties. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Property Type. The "Evaluation Ordering" VLDB setting affects the order in which the Analytical Engine will perform various calculations. MicroStrategy 9. It is recommended to always stay on the latest MicroStrategy release so you can always have the best Snowflake experience out of the box. There are a number of them. One of the options under Analytical Engine folder is called "Metric Level Determination. Open “Database instances” in the Categories menu, and click on “SQL Data warehouses”. Open navigation menu. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. This setting is useful if you have only a few attributes that require different join types. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. Doc Preview. This syntax can be costly for most Relational Database Management System (RDBMS) platforms when the fact tables involved are large in size. 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. However, this could produce inflated subtotal or dynamic. 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. It is recommended to always enable secure text input. Since MicroStrategy Analytical Engine 9. x still supports third-party gateway solutions. Select either Disable or Enable depending on whether you want to disable or enable. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. This VLDB setting can be changed at the Database instance, Report, and Metric levels. 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 VLDB property has the following options: Disable parallel query execution (default) : All queries for MicroStrategy reports and Intelligent Cubes are processed sequentially. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". The upgrade database type window appears. A simple metric sum (Revenue) will go to different aggregate tables depending on the attributes on the template. The attribute level follows a consecutive order from. Metric-specific VLDB properties that can be set at the metric level include. Beginning with MicroStrategy 8. From the Tools menu, select Set all values to default. Click Properties. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. The Null Checking for Analytical Engine VLDB property determines whether or not null values are interpreted as zeros when the Analytical Engine calculates data. VLDB properties allow you to customize the SQL that MicroStrategy generates. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. Description. To set these properties, right-click a project within the database instance to be updated. 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. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the. the Report Data Options. In the Report Editor click on 'Data'> 'VLDB Properties' option, as illustrated below. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Choose Tools > Show Advanced Settings option if it is. In MicroStrategy 10. Click Save and Close to save your changes. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. MicroStrategy can support multiple (more than 5) pre-statements to put in a report. For detailed information on VLDB Properties, see the MicroStrategy Supplemental Reference for System Administration. x, "Use relational model" is selected by default. After the project information is processed, you are returned to MicroStrategy Developer. -1 (Use value from higher level) Limiting Report Rows, SQL Size, and SQL Time-Out: Governing. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. col1, s1. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. " Save and close. 2. The VLDB property's behavior will be demonstrated using the following attribute and report. a. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Right-click on an existing environment and choose Properties. 1 and 10. Clear the Use default inherited value check box. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". See the Advanced Reporting Help. 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. From the Data menu, select VLDB Properties. You can manipulate things like SQL join types, SQL inserts,. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. If a table has been imported from only one database instance, the secondary database instance panel will be empty and disabled. 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. To begin, the architecture for dashboard execution is. Certain VLDB properties exist at the database instance level but are viewed by the SQL Engine as unrelated to the database used. To modify the String Comparison Behavior VLDB property for an attribute. 1 and 10. 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. View full document. . Below are the list of parameters that the URL must. See Details for All VLDB Properties for more information. Certain VLDB properties use different default settings depending on which data source you are using. Right-click a database instance and select Edit. Within here there are. Details of Document Execution Request, introduce the Performance Troubleshooting Cycle, and present links to other resources with detailed steps for troubleshooting specific components that may affect performance. Choose the database instance and then open VLDB Properties. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. 4. However, you want to show all the store. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. MicroStrategy has specific order in the from clause. 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. 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. 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 set of unrelated VLDB properties includes the Metric Join Type setting. For steps, see the MicroStrategy Developer help.