You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. 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. VLDB properties also help you configure and optimize your system. From the Tools menu, select Create VLDB Settings Report. . MicroStrategy Office privileges. Additional VLDB Settings. Specifying the Display Mode and VLDB Properties. It also displays all current settings for each VLDB property. 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. Local temporary tables, indicated with the "#" character, are stored in tempdb and incur less overhead. 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. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. MDX cubes are also referred to as MDX cube sources. The options for this. The Preserve all lookup table elements. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. In Web: Click the MicroStrategy > Preferences. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. But the grid is not reset properly when adding and removing a derived element. From the Tools menu, select Grouping. Clicking in Preserve all pass the final elements option. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. In the Report Editor click on 'Data'> 'VLDB Properties' option, as illustrated below. However, each database instance is allowed to have its own VLDB property values. The following list summarizes the metric-specific VLDB properties that can be set at the metric 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. Open âDatabase instancesâ in the Categories menu, and click on âSQL Data warehousesâ. Select the radio button labeled "Outer Join. 15. Any existing projects will retain the null checking behavior that was. 192 Determining the level to apply a VLDB property. Open the database instance for the project. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Dimensionality Model. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". x, select 'Project Documentation' from the Tools menu to start the wizard. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. In MicroStrategy 10. Some queries may benefit from distributing data by the fact columns as well as the attribute ID columns. 4. A few common one are for Attribute or Metric join types, cross join check, type of intermediate table, etc. The "Evaluation Ordering" VLDB setting has two possible values, "6. DATA ANALYSIS. MicroStrategy uses a user editable XML file to control what VLDB properties are visible in the different GUI parts of MicroStrategy client products. Changes made to this VLDB setting can cause differences to appear in your data output. Additionally, the COALESCE function can be included in the SQL query. VLDB properties allow you to customize the SQL that MicroStrategy generates. col1, s1. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. Click on. 2. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. For detailed information on VLDB Properties, see the MicroStrategy Supplemental Reference for System Administration. " Save and close. Possible locations for VLDB optimizations in the query structure are listed below. The most basic DBMS (database) level where properties are defined. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. 4. QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. 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. Choose one of the following: â˘. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. These settings affect how MicroStrategy Intelligence Server. VLDB_PROPERTY_NAME: The. Accessing Report VLDB Properties. The Parallel Query Execution property determines whether MicroStrategy attempts to execute multiple queries in parallel to. 2. MicroStrategy application developers can further optimize SQL for their specific Oracle environment using these string insertion settings. The recommended VLDB optimizations for Oracle 11g are listed below. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. 3. x. â˘The filter on [MONTH_ID] is applied to the lookup table because the VLDB property dictates so. If you choose Temp Table Join. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. MicroStrategy application developers can further optimize SQL for their specific SAP HANA environment using string insertion settings. In the bottom left corner, click on the button "Generate Connection File". Attribute. In MicroStrategy, there is a Very Large Data Base (VLDB) property, "Additional Final Pass Option," that configures whether or not the engine will optimize SQL into a single pass when possible. Both the SQL Date Format and. It is very. When selected, the options and SQL, if applicable, appear in the right side of the dialog box. Execute the report and view the SQL:September 06, 2018. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. Then go to the key âQuery Optimizationâ > âData Population for Intelligent Cubesâ and choose the optimal option. PDS file. The Project Configuration Editor opens. KB441418: Supplemental reference for installing Hotfix on MicroStrategy version 10. 3. " In MicroStrategy SQL Generation Engine 8. " Uncheck the "Use default inherited value" checkbox. Under Query Optimizations, select SQL Global Optimization. 2. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. The user should locate the VLDB. Go to Metrics > NULL Check. VLDB properties also help you configure and optimize your system. 1, the VLDB property âAnalytical Engine > âFiltering on String Valuesâ has been available at project level. Community & Support Search Discussions Open A Case View My Cases1. From the Tools menu, select Set all values to default. Zillow has 471 homes for sale in Victoria BC. VLDB_PROPERTY_VALUE: The value of the property, returned as a string. For examples and details to enable these properties, see SQL Generation and Data Processing: VLDB Properties. In the VLDB Editor open the 'Tables' folder and click on 'Intermediate Table Type. See the Advanced Reporting Guide. g. However, there is no governing for in-memory executions, including data blending which creates unnecessary risk to the stability and performance of the. Q22) What are VLDB properties? Ans: VLDB stands for Very Large Data Base Properties. You can manipulate things like SQL join types, SQL inserts,. The MDX cube report is executed. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". This section tells you how to do the following:VLDB properties let you to customize the SQL that MicroStrategy generates when a report is executed, and determine how data is processed by the Analytical Engine. 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. To the right of the Database connection area, click Modify. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Description Understanding your data characters and choosing the matched. In the Attribute Editor, on the Tools menu, select VLDB Properties. . The Database Connections dialog box opens. Follow the steps below to change the property. There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. x. 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. Group by position. Then go to the key âQuery Optimizationâ > âData Population for Intelligent Cubesâ and choose the optimal option. Topics Introduction to the MicroStrategy engine Basic optimizations Templates Metrics Filters The. Database instances for the project source are displayed. 2) In Joins, select Preserve all the final pass result elements. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. However, you want to show all the store. List all parent groups of a user group 'sGroup'. Why MicroStrategy Why MicroStrategy; Customer Stories; Platform Products; MicroStrategy ONE; AI & Augmented; Dossier; Library; Workstation; HyperIntelligence; Multi-Cloud; Embedded Analytics; Innovations; Futures. Database Instance Level This is the most common place to set VLDB Properties. Here, we will use MicroStrategy Tutorial objects. If you have selected multiple reports, including bulk export reports, and choose the Run Report option from the right-click menu, all the bulk export reports are filtered out and are opened in the Report Editor; the other reports. See Details for All VLDB Properties for more information. Log in to a project in MicroStrategy Developer. This file can be modified to add additional VLDB properties to display in case non standard properties need to be changed in an environment. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. It is recommended to always stay on the latest MicroStrategy release so you can always have the best Snowflake experience out of the box. In MicroStrategy SQL Generation Engine, the VLDB property "Preserve all final pass result elements" is designed for the case in which data elements exist in a fact table that are missing from an attribute's lookup table. x and later). For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. Total views 28. This property is called 'MDX TopCount Support' and is available at the report level and database instance level. x order - Calculate derived metrics/smart compound metric before derived elements/consolidation and all subtotals are smart" and "7. Use the VLDB Properties Editor to change the defaults to alter the syntax of a SQL statement and take advantage. 4. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. 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. 4. Click the Load button. To access the setting, in MicroStrategy Developer right-click on the project and select Project ConfigurationâŚThen, In the Project Configuration dialog box, choose Project Definition >. There is a method to change the default syntax for table and column names while generating MicroStrategy SQL during report execution in MicroStrategy by using VLDB properties. 1 and 10. In Developer, from the Tools menu, select Developer Preferences. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. Based on these VLDB (Very Large Data Base), the Intelligence server manages the query optimization, calculations, and metrics. This section includes the following. For a data source, right-click it and choose Edit. In MicroStrategy 10. By default, MicroStrategy generates SQL creating the primary index on all attribute ID columns that are used in the intermediate table. . Additional details about each property, including examples where necessary, are available by clicking on the links in the table. 3. Pages 100+ Identified Q&As 2. This information is available for each property in the VLDB Properties dialog box at each level. You can check out the 3 options in VLDB Properties / Joins / From Clause Order While you are there, check out the last option under VLDB. Changing an option in one of the editors automatically reads the changes and is reflected in the other editor as well. Open your report in the Report Editor. The VLDB Properties Editor opens. Both properties are located in the Query Optimizations folder in the VLDB property editor. â This property can be found at the project (database instance), template and report levels. 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. <Setting> If that level is also set to the default or if the VLDB property is not set at the project level, the setting at the database instance is used. In the lower-right. When you change a VLDB property setting at the database instance or project level, you must restart Intelligence Server for the MicroStrategy Engine to read the latest schema information from the metadata. However, you want to show all the store. The following settings are advanced properties which are. Use the temp table prefix in the (Very Large Database) VLDB properties window. 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. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. (The original name for this property, in fact, was "Incomplete lookup table. Victoria's peaceful atmosphere and vibrant real estate market make it a great place to search for your next home. This VLDB property is useful only for MDX cube reports that access an Oracle Hyperion Essbase MDX cube source. In the confirmation window that appears, click Yes. ' If the check box 'Use default inherited value' is checked, then check this setting at the Database Instance (project) level; otherwise increase the value to a number (this is in seconds and 0 means no time out) that suits the report. For more details, go to Start -> Programs -> MicroStrategy -> Product Manuals -> Advanced Reporting Guide (PDF) -> 13. Subqueries (or correlated subqueries) are used infrequently but significantly in the MicroStrategy SQL Generation Engine. The following diagram shows how VLDB properties that. Viewing and Changing VLDB Properties. All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. Click VLDB Properties. This syntax can be costly for most Relational Database Management System (RDBMS) platforms when the fact tables involved are large in size. 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. KB31580: Recommended VLDB Properties for use of MicroStrategy 9 with Teradata 12 (and higher) as a warehouse. See the warning above if you are unsure about whether to set properties to the default. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Click the "VLDB Properties. MicroStrategy TutorialPublic ObjectsReportsMicroStrategy Platform CapabilitiesAd hoc ReportingSortingYearly Sales!i inserts the. Under the VLDB properties for the report, change the Additional Final Pass Option setting to One. See the screenshot below:In the Select Configuration dialog, go to Project definition > Advanced. The VLDB Properties Editor opens. (In MicroStrategy Developer, navigate to VLDB Properties > MDX > MDX Cell Formatting. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Throughout the course, students gain hands-on practice via a series of exercises. Modify the VLDB property you want to change. 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). The default option is for aggregation calculations to ignore nulls and for scalar calculations to treat null values as zero. Expand the Governing settings, then select Results Set Row Limit. These tables can either be 'permanent' or 'true temporary'. Enter the desired location under 'Database name' in the 'Intermediate table storage' section. Click on the upgrade button. Click Save and Close to save your changes. The VLDB properties at the different levels work together to affect report results; however, there is a different interface for each level. Properties set at the report level override properties at every other level. . After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. 6 In the VLDB Properties Editor, in the Indexing section, change the Intermediate Table Index setting from the default to Create only secondary index on intermediate table. Right click on your project and click âProject ConfigurationâŚâ. You can configure properties. x, outer joins are designed to get all the data from the lookup tables. Also, the Project level settings contain the Analytical Engine-related VLDB properties and the MDX VLDB properties. 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. 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. Default VLDB properties are set according to the database type specified in the database instance. This article covers the purpose of the where clause driving table property. Deliveries privileges. 4. Project-Level VLDB settings: Click to configure the analytical engine settings. VLDB (Very Large DataBase) properties allow you to customize the SQL that MicroStrategy generates. See the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help) or the System Administration Help for steps to set this VLDB property. Loading × Sorry to interruptGo to Data > VLDB Properties > Tables > Intermediate Table Type, change it to "Common table expression". Choose the database instance and then open VLDB Properties. The attribute uses a CASE statement to replace NULL values with -999. 203 Exercise 7. VLDB is an acronym for You answered: Very Large Database Incorrect Correct answer: Very Large Database properties 13. Several additional VLDB properties are introduced with MicroStrategy 9. Set up the VLDB settings for metric join type and SQL GO. It sets the general standards. To be effective. Project. Select the radio button labeled "Outer Join. The MicroStrategy SQL Generation Engine provides a Very Large Database (VLDB) property Called âGROUP BY Non-ID Attribute. 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. Then select MDX metric values are formatted by column (default) or MDX metric values are formatted per cell. Case 3: Cross Join due to the VLDB setting Downward Outer Join Option. For this scenario, you can use these two VLDB properties to define which MicroStrategy data types support the character sets of your Teradata database. Among all , Report has highest priority and It always override the others . The full set of VLDB properties is documented in the MicroStrategy System Administration Guide. Description. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB properties is via. Parallel Query Execution is an advanced property that is hidden by default. For a data source, right-click it and choose Edit. Click the Joins folder to expand it and then choose Preserve all lookup table elements. A given VLDB setting can support or. Any projects that existed prior to upgrading metadata to MicroStrategy 2020 retain their original VLDB property settings. The Project Configuration Editor opens. VLDB_PROPERTY_NAME: The. 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". On the Advanced tab, select the Use parameterized queries check box. (For information on object levels, see Order of Precedence . The maximum number of rows returned to the Server for the final result set. . All VLDB properties that are displayed in the VLDB Properties Editor are returned to their default settings. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. The VLDB Properties Editor opens. 4. Group by column. 1 and 10. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. This article explains the behavior of the commit level VLDB propertyThe MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. â˘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. It means in most cases, the subquery expression will be generated by creating temporary table:To Configure a Report for Bulk Export. This section focuses on the VLDB properties that are set at the metric and report level. x For MicroStrategy reports that generate multi-pass SQL with temporary tables, it is sometimes desired that that description form of an attribute is also selected in the temp table along with the ID form. 1) From the Data menu, access the VLDB Properties option. Allows the MicroStrategy SQL Engine to use a new algorithm for evaluating whether or not a Cartesian join is necessary. 4. 5. 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. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Double-byte language support. Certain attribute-to-attribute comparisons may require subqueries. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Then go to the key âQuery Optimizationâ > âData Population for Intelligent Cubesâ and choose the optimal option. Web Analyst privileges. The table b elow summarizes the MultiDimensional Expression (MDX) related VLDB properties. x order - Calculate. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Open the Workstation window. Micro Strategy Interview Questions and Answers - Free download as PDF File (. In order to export a document in excel format using the URL API, the executionMode must be set to 4. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. MicroStrategy implements a list of strategies through VLDB settings to generate temp table for the efficient execution of complex business queries. The Year - Define a new member attribute. The Database Instances Editor opens. You can determine the default options for each VLDB property for a database by performing the steps below. Database Instance > VLDB Properties Report Level: Data > VLDB. In MicroStrategy Developer, open a report in the Report Editor. ; 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. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. 4. The VLDB property, Attribute to Join When Key From Neither Side can be Supported by the Other Side becomes obsolete once you upgrade your data engine version to 2021. Clear the Use default inherited value check box. The two possible values are as. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. 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. The properties are saved in different folders, as indicated in the previous list. In the VLDB Properties dialog go to the menu: Tools > Show Advanced Settings. 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. . Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. You can specify another. 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. 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. Join common key on both sides. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Introduction to VLDB Properties Optimizing processing with VLDB properties. 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. x order - Calculate. x has changed the default value of the "SQL Global Optimization" VLDB property. They are exactly the same. From the Data menu, select VLDB properties. (This exception case is supported in MicroStrategy 2020 Update 5 and above, MicroStrategy 2021. ) From the Tools menu, select Show Advanced Settings. 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. Open Database Instance Manager in MicroStrategy Developer and click on the Advanced tab. VLDB properties (sometimes called VLDB settings) allow you to customize the SQL that MicroStrategy generates. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the. 3) In Joins, select Join Type. 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. 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. A possible business case that could be solved by this approach: A large fact table that summary reports are sourcing, from which it is necessary to drill down through a report (or report template) to row level data. 8/7/2021. mstr) file size (MB) setting. You must have the " Use VLDB property editor " privilege to make changes to the setting. Contact MicroStrategy. 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. To access the VLDB properties editor at the project level in the MicroStrategy Cloud Environment, please use either a Desktop Designer or Architect user account to connect to MicroStrategy Developer. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. This controls whether the MDX function TopCount is used in place of Rank and Order to support features such as metric qualifications. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Certain VLDB properties use different default settings depending on which data source you are using. 0. The attribute level follows a consecutive order from. The table b elow summarizes the Export Engine VLDB properties. Beginning with MicroStrategy 8. In some cases the drill, unrestricted, could. Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of levels in hierarchy * 10). 0. Normally, MicroStrategy SQL Generation Engine attempts to combine metric calculations and attribute lookups into one pass of SQL. VLDB properties can provide support for unique configurations. 5 : If the Use default inherited value check box is selected, clear it. In MicroStrategy Developer, open a report in the Report Editor. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHyperIntelligence and its Architecture. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. In the Results Set Row Limit field, type the limit. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. Web Professional privileges. Possible locations for VLDB optimizations in the query structure are. These values are set by default when the "Teradata 12" database object is used (set at Configuration Managers > Database Instances > Database Instance. Common privileges. 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 Settings list, expand Dynamic Sourcing, and then select Enable Dynamic Sourcing for Report. XQuery Success Code is an advanced property that is hidden by default. The following.