Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. To overcome these challenges, we first analyze a real-world query trace from Snowflake and compare its properties to that of TPC-H and TPC-DS. When creating attribute relationship filters, the default Very Large Database (VLDB) property for sub query types causes EXISTS statements to appear in the sub queries. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. 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. In the Project Configuration Editor, expand Project definition, and select Advanced. Exporting Report Results from MicroStrategy: Export Engine. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. 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". 5. In MicroStrategy 7i, new methods were introduced to evaluate the calculation level of metrics which prevent the incorrect result demonstrated in this document. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. 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. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. Under Project-Level VLDB Settings, click Configure. Under Query Optimizations, select SQL Global Optimization. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". Metrics using count or average, metrics with dynamic aggregation. Under 'Database instances', select VLDB Properties. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. •. Click Save and Close. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. If the report result set exceeds the limit specified in the Result Set Row Limit, the report execution is terminated. If this VLDB property is not displayed, you must upgrade the project metadata. From the Tools menu, select Show Advanced Settings. VLDB properties also help you configure and optimize your system. Possible locations for VLDB optimizations in the query structure are. Choose the database instance and then open VLDB Properties. Enable. ) From the Tools menu, select Show Advanced Settings. The setting will NOT force the MicroStrategy Engine to include the [LU_ITEM] table. For more details, go to Start -> Programs -> MicroStrategy -> Product Manuals -> Advanced Reporting Guide (PDF) -> 13. ; Click the General tab. Lets you identify attributes that include empty elements, which can then be ignored when. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. This feature provides the ability to create multiple query queues and queries are routed to an appropriate queue at runtime based on their user group or query group. Description. One of the options under Analytical Engine folder is called "Metric Level Determination. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. Click the Joins folder to expand it and then choose Preserve all lookup table elements. XQuery Success Code is an advanced property that is hidden by default. To help illustrate the functionality of the property, consider an unbalanced hierarchy with the levels Products, Department, Category, SubCategory, Item, and SubItem. This section tells you how to do the following:When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. On MicroStrategy Web and Workstation, the same. View listing photos, review sales history, and use our detailed real estate filters to find the perfect place. Lookup Tables VLDB Settings provide minimal modifications to this order. It can be enabled on project level: Open MicroStrategy Developer. (For information on object. Change the VLDB setting . When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. 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. See Template Editor. Choose Data > Configure Bulk Export. In MicroStrategy Developer 9. Project. A report is generated that displays all VLDB properties available at the level from which you accessed the VLDB Properties Editor. How to change the syntax is described in detail by using examples. The maximum number of rows returned to the Server for the final result set. At the report level, change the. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. To set these properties, open the report in the Report Editor or Report Viewer. Under the VLDB properties for the report, change the Additional Final Pass Option setting to One. MicroStrategy has specific order in the from clause. Throughout the course, students gain hands-on practice via a series of exercises. Specifying the Display Mode and VLDB Properties. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. Each queue is defined by concurrency level, user groups, query groups, wild cards, memory percent to be used,. How to create a MicroStrategy connection file (. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. 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. Click VLDB Properties. On the Freeform Sources tab, select Create Freeform SQL report. Many of the VLDB properties control string syntax used in SQL queries generated by the MicroStrategy SQL engine. By default, all properties are governed by the one at the top level. Click Save and Close to save your changes. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. 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. Join common key on both sides. Group by column. Group by alias. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. In some cases the drill, unrestricted, could. Metrics using count or average, metrics with dynamic aggregation. Set the additional final pass property to force an additional pass of SQL. This article explains how to migrate VLDB Select propertyset from an older metadata to a newly created metadata. Any projects that existed prior to upgrading metadata to MicroStrategy 2021 retain their original VLDB property settings. Right click on your project and click “Project Configuration…”. List Projects That User Has Access ToInformation and instructions for MicroStrategy administrative tasks such as configuring VLDB properties and defining data and metadata internationalization, and reference material for other administrative tasks. Any projects that existed prior to upgrading metadata to. 0, a VLDB property is available to control. XQuery Success Code is an advanced property that is hidden by default. Local temporary tables, indicated with the "#" character, are stored in tempdb and incur less overhead. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. It sets the general standards. Select a SQL Global Optimization level. From the Data menu, choose VLDB Properties. x order - Calculate. This article covers the purpose of the where clause driving table property. Published: 4월 6, 2017. In MicroStrategy Developer, open a report in the Report Editor. However, you set. You can manipulate things like SQL join types, SQL inserts,. 2021 Update 7 (September 2022) MicroStrategy Workstation. The attribute uses a CASE statement to replace NULL values with -999. Group by column. 5 From the Data menu, select VLDB Properties. link MicroStrategy users and groups to users and groups from sources such as Windows NT, LDAP, or a database:VLDB properties allow you to customize the SQL that MicroStrategy generates. You can determine the default options for each VLDB property for a database by performing the steps below. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. 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. Some queries may benefit from distributing data by the fact columns as well as the attribute ID columns. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. This set of unrelated VLDB properties includes the Metric Join Type setting. mstr) files that can be sent through Distribution Services is defined by the MicroStrategy (. x. x, the only options were to drop tables or do nothing. In MicroStrategy Developer, log in to a project. txt) or read online for free. You can specify another. Loading × Sorry to interruptGo to Data > VLDB Properties > Tables > Intermediate Table Type, change it to "Common table expression". This file can be modified to add additional VLDB properties to display in case non standard properties need to be changed in an environment. Follow the steps below to change the property. See Details for All VLDB Properties for more information. Export to PDF filter summaries include the full attribute and metric names. For more details, go to Start . When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. Join common key on both sides. Additional details about each property, including examples where necessary, are available by clicking on the links in the table. Group by position. To View and Change Attribute Join Types. 0. (For information on object levels, see Order of Precedence . Upgrading Your Database Type Properties. This information is available for each property in the VLDB Properties dialog box at each level. These VLDB properties control the method by which the report data are normalized. Intermediate Table Type . The option "SQL Global Optimization" under Query Optimizations is not available when a report VLDB properties need to be changed. 1, this can be done at the report level by following the steps in technical note 10073. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. When the grand total metric and another metric exists on a grid, Cross Join is produced to join to grand total metric and is exempted from the Cartesian Join Governing property. Dependent Object Options: Enable Find and Replace object dependencies: If the checkbox is selected, a user is allowed to find all dependent objects and replace them. A common request is to set a higher priority for element browsing requests only, because they are generally very simple queries, and slow execution directly impacts the user's perception of the project's responsiveness by delaying the appearance of prompts. Click the "VLDB Properties. MicroStrategy supports reporting and analysis with SAP BW, Microsoft Analysis Services, Hyperion Essbase,. See Viewing and Changing Advanced VLDB Properties for more information on how to display this property. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the (missing or bad snippet) for steps to set this VLDB property. ; 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. The. . x where report SQL statement containing semi-colon (;) in the Report Pre Statement 5 VLDB properties will cause report to fail in MicroStrategy 10. 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 ). 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). This syntax can be costly for most Relational Database Management System (RDBMS) platforms when the fact tables involved are large in size. To be effective. Based on these VLDB (Very Large Data Base), the Intelligence server manages the query optimization, calculations, and metrics. 4. It also displays all current settings for each VLDB property. 4. When using a Snowflake database it may appear that the Metric Outer join option is turned on. User changing own language. x. This setting is called Join Across Datasets. 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. In. However, each database instance is allowed to have its own VLDB property values. Accessing Report VLDB Properties. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. If the SQL of your Report has any Sub queries, You can use the “Use Temporary Table” option available in Query Optimization in VLDB Properties. For this reason, two additional options are provided:Export to PDF: export a report or document to a PDF document: EXPORTTOPDF:. The default syntax can be modified by using 'Column Pattern' VLDB property. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. Additionally, the COALESCE function can be included in the SQL query. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. 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. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". The Microstrategy SQL that has been generated can be customized using the VLDB properties. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. The VLDB Properties Editor opens. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. Open MicroStrategy Developer. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. See the Advanced Reporting Guide. The dimensional model is included for backward compatibility with MicroStrategy 6. 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 index for referencing these objects begins with 0 and increases by for each successive object passed. 4. Parallel Query Execution. The table b elow summarizes the Export Engine VLDB properties. This information is available for each property in the VLDB Properties dialog box at each level. You can specify another. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. It is strongly encouraged that you post your questions on the community forum for any community based. As shown in the example above, all data for cost is aggregated together and shown for every row of a category. Remove the training metric from the report. 4. Since full outer joins can require a lot of database and Intelligence Server resources, and full outer joins are not supported for all databases, it. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. (For information on object levels, see Order of Precedence . Integer Constant in Metric; Metric Join Type; Null Check; Zero CheckThis manual runs through VLDB Properties, Internationalization, User Privileges, and Other Supplemental Information for Administrators. 4. pdf - MicroStrategy. Several additional VLDB properties are introduced with MicroStrategy 9. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. The report SQL shows that the first metric is calculated at the level of Quarter (report. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform14. To identify attributes that include empty elements, type the ID value for each attribute in the text field for this VLDB property. 3. Check the option according to the database used. The recommended VLDB optimizations for Oracle 11g are listed below. If a table has been imported from only one database instance, the secondary database instance panel will be empty and disabled. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. The VLDB properties at the different levels work together to affect report results. 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. •Students review the most commonly used VLDB properties in certain categories, such as indexing, joins, pre/post statements, query optimizations, and tables. MicroStrategy SQL Generation Engine 9. MicroStrategy’s VLDB driver for Azure SQL Data Warehouse is designed to use SQL DW-specific features when they lead to improved performance or analytical functionality. SUMMARY: This document shows one issue that a dvanced VLDB properties don't show up when "Show Advanced Settings" is enabled in MicroStrategy Developer 10. NIT Rourkela. VLDB properties can provide support for unique configurations. Under Categories, expand Calculations, and select Attribute Join Type. List all reports that do not use default VLDB settings in the folder 'folder' for the project 'project', and the VLDB properties in those reports that do not use default settings. Victoria is a good city to buy a house in for those who prefer a slower-paced atmosphere. Use the SQL Date Format VLDB property to format the date string to match the attribute's description (MEMBER_NAME property in the cube). A given VLDB setting can support or. If you choose Temp Table Join. On the Advanced tab, select the Use parameterized queries check box. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. The MDX cube report is executed. txt) or read online for free. Details for All VLDB Properties Modify VLDB properties with caution and only after understanding the effects of the VLDB settings you want to apply. Set up the VLDB settings for metric join type and SQL GO. This. In the VLDB Properties window, expand the folder called. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. A few common one are for Attribute or Metric join types, cross join check, type of intermediate table, etc. 5. In the latter case, intermediate tables would be left on the database; administrators could remove them using a database-side scheduled task. Database instances for the project source are displayed. 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. DATA ANALYSIS 102. 4. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Notice that the 4 options shown on the upper right are the same as those in the VLDB dialog box (internally they are read from the same location). The following list summarizes the metric-specific VLDB properties that can be set at the metric level. VLDB_PROPERTY_GROUP_NAME: The group name associated with the project, returned as a string. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. How to change the syntax is described in detail by using examples. Changes made to this VLDB setting can cause differences to appear in your data output. The Database Connections dialog box opens. There are number of them. 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. Click Save and Close to save your changes. Sometimes pre-statement VLDB Properties are used to set database priority. 5 : If the Use default inherited value check box is selected, clear it. Single Sign-On (SSO) allows for one-time login for both MicroStrategy and Snowflake. . x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". OR. Choose Data > Report Data Options. Select VLDB Properties from the Data menu. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. 15. 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. 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. Check the report SQL, and observe that permanent tables are still used as intermediate tables. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. 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. You can use this setting on the following levels: To edit the setting, you must have "Use VLDB property editor. x has changed the default value of the "SQL Global Optimization" VLDB property. Multiple passes are generated only when necessary to resolve all the metric definitions. Expand the 'Administration' Icon, and select the Database Instance Manager. 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. 7 Click Save and Close in the VLDB Properties Editor. This is a Microstrategy way of handling database-specific preferences while generating the report SQL. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base technical note: When the grand total metric and another metric exists on a grid, Cross Join is produced to join to grand total metric and is exempted from the Cartesian Join Governing property. the VLDB property is set to the Preserve common elements of final pass result table and lookup table option. 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. 8 From the File menu, click Save As. MicroStrategy periodically updates the default settings as database vendors add new. For a data source, right-click it and choose Edit. These settings affect how MicroStrategy Intelligence Server. From the Data menu, choose VLDB Properties. MicroStrategy can support multiple (more than 5) pre-statements to put in a report. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. In the lower-right. Right-click on an existing environment and choose Properties. Diagnosis. 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. The MicroStrategy Tutorial project uses aggregate tables by default. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. The following list offers a detailed trace of each property available in Developer and its new place in MicroStrategy’s modern tools, such as Workstation. The attribute level follows a consecutive order from. The system reads them from the same location. Open the report template in the Template Editor. 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 MicroStrategy SQL Generation Engine provides a Very Large Database (VLDB) property Called “GROUP BY Non-ID Attribute. For new installations of MicroStrategy 8. Now your connection f. 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. WHERE (col1, col2) in (SELECT s1. " button under the warehouse name, as shown below: Open the "Metrics" folder and select "Metric Join type. !o inserts the report name (can be used in all Pre/Post statements). Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. 1 and 10. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". 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 VLDB Properties Editor opens. Base Table Join for Template. x introduces a third option to the VLDB Property "Drop Temp Table Method. x. 2. However, you want to show all the store. Certain attribute-to-attribute comparisons may require subqueries. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. For more information about all the VLDB properties, see SQL Generation and Data Processing: VLDB Properties. Double-byte language support. Make sure the Use default inherited value check box is cleared. But the grid is not reset properly when adding and removing a derived element. The Project Configuration Editor opens. Additional VLDB Settings. 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. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results. Web Professional privileges. Order of Precedence. Use this section to learn about the VLDB properties before modifying any default settings. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. x. The table b elow summarizes the Pre/Post Statements VLDB properties. MicroStrategy ONE introduces new features that provide better performance and scalability to enhance the overall user experience. Check the SQL generated by MSTR is good (without cross joins) Check for the execution plan on database. See Details for All VLDB Properties for more information. . These settings are passed to the specific report/job VLDB properties only from the project primary database instance. It is strongly encouraged that you post your questions on the community forum for any community. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. Intermediate Table Type . Very Large Database (VLDB) properties are settings in charge of performing database specific optimizations (customizing Structured Query Language (SQL)). The Database instances - SQL Data warehouses pane displays. 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. A given VLDB setting can support or optimize one system setup, but the same setting can cause performance issues or errors for other systems. The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3. The VLDB Properties Editor opens. Property Type. If this is required by MicroStrategy Technical Support for trouble-shooting an issue, copy and paste the contents of this report into notepad and send it. (0 = unlimited number of rows; -1 = use value from higher level. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. Choose Data > Configure Bulk Export. QUARTER_ID QUARTER_ID, KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. x has changed the default value of the "SQL Global Optimization" VLDB property. In order to export a document in excel format using the URL API, the executionMode must be set to 4. 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. MicroStrategy Office privileges. The following settings are advanced properties which are. wanttobuildandresellMicroStrategy-basedproductsorapplicationssuitedto particularindustries. Relationship Tables 4. 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. In MicroStrategy 10. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work.