To create and review a detailed list of all the default VLDB settings for different DBMS types, see Default VLDB Settings for Specific Data Sources. To configure it, open the Project. 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. 4. NOTE: For information regarding the hierarchy of the different MicroStrategy VLDB settings, refer to the following MicroStrategy Knowledge Base. The Database Instances Editor opens. Diagnosis. However, you want to show all the store. . Changing an option in one of the editors automatically reads the changes and is reflected in the other editor as well. This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. You can determine the default options for each VLDB property for a database by performing the steps below. LIST VLDBSETTINGS GROUP VLDB_PROPERTY_GROUP: A ResultSet containing a list of properties associated with a group. Since these financial line item attributes include empty elements to support the hierarchical structure of the financial data, this causes some of the rows of the exported report to also be empty. WHERE (col1, col2) in (SELECT s1. 3. Open a grid report. <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. Export a Report Services document to Excel with formatting using URL API in MSTR Web. After the Administrator sets up SSO, they only have to login once and take advantage of both MicroStrategy and Snowflake from the same credentials. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. This occurs when the data type of the attribute is timestamp. Determines whether MicroStrategy attempts to execute multiple queries in parallel to return report results faster and publish Intelligent Cubes. Contact MicroStrategy. 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. The Database Connections dialog box opens. The attribute level follows a consecutive order from. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. MicroStrategy SQL Generation Engine 9. Based on these VLDB (Very Large Data Base), the Intelligence server manages the query optimization, calculations, and metrics. Dimensionality Model is an advanced property that is hidden by default. For information on connecting to databases, see Connect to Databases. The system reads them from the same location. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. 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. View listing photos, review sales history, and use our detailed real estate filters to find the perfect place. 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. Additional details about each property, including examples where necessary, are available by clicking on the links in the table. Single SQL pass time-out in seconds. Select the radio button labeled "Outer Join. For example, if a VLDB property is set one way for a report and the same property is set differently for the database instance, the report setting takes precedence. The table b elow summarizes the Export Engine VLDB properties. The table b elow summarizes the Query Optimizations VLDB properties. 4. Join common key on both sides. In MicroStrategy Developer, open a report in the Report Editor. One of the options under Analytical Engine folder is called "Metric Level Determination. x order - Calculate. 1 includes a new VLDB property, Custom Group Display for Joint Elements'. 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. •[COUNTRY_ID] exists in the lookup table and this table is already present in the FROM clause, so it can indeed be extracted from the lookup table. It is recommended to always enable secure text input. If a message saying that the type already exists, click on Yes to update it. 7 Click Save and Close in the VLDB Properties Editor. Dashboard performance troubleshooting in MicroStrategy 10. 8 From the File menu, click Save As. This property determines how values for metrics are calculated when unrelated attributes from different datasets of a dossier or document are included with metrics. Fact Tables 2. Victoria's peaceful atmosphere and vibrant real estate market make it a great place to search for your next home. Select the radio button labeled "Outer Join. 2021 Update 7 (September 2022) MicroStrategy Workstation. Below are the list of parameters that the URL must. They can be set at different levels throughout a project to establish a specific behavior regarding the object type. x and later). There is one VLDB property in MicroStrategy that controls the join behavior between different datasets. Click Save and Close to save your changes. 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. g. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. In this course, you will study specific reporting scenarios and the MicroStrategy Engine’s techniques for composing the SQL queries that produce MicroStrategy reports. DATA ANALYSIS 102. VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. 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. Access the VLDB Properties Editor. Specifying the Display Mode and VLDB Properties. Topics Introduction to the MicroStrategy engine Basic optimizations Templates Metrics Filters The. 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. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Based on these VLDB (Very Large Data Base), the Intelligence server manages the query optimization, calculations, and metrics. It is strongly encouraged that you post your questions on the community forum for any community based. Upgrading Your Database Type Properties. Disable parallel query execution (default): All queries for MicroStrategy reports and Intelligent Cubes are processed sequentially. Please right-click a project>Project Configuration>Database Instances>VLDB Properties (for the appropriate database instance) to access the VLDB properties. •Students review the most commonly used VLDB properties in certain categories, such as indexing, joins, pre/post statements, query optimizations, and tables. Impact: Authentication Motivation: One-time login Details: MicroStrategy currently support SSO with Azure AD. . The method used for multiple data source access is controlled by a project-level VLDB Property. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. The Database Instances Editor opens. 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. To set these properties, right-click a project within the database instance to be updated. x, outer joins are designed to get all the data from the lookup tables. Metric Qualification (MQ) Tables 3. 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. Click the "VLDB Properties. These properties govern the working of the Analytical and SQL Engine, which have a significant influence on the business reports. To Configure a Report for Bulk Export. •. 4. For example, the report shown below ranks the NULL values. The full set of VLDB properties is documented in the MicroStrategy System Administration Guide. col1, s1. The VLDB Properties Editor opens. Currently this issue is being reviewed by MicroStrategy for a potential enhancement request on an upcoming MicroStrategy release. This property is report-specific. " In MicroStrategy SQL Generation Engine 8. VLDB Settings These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. To address this issue, a VLDB property called "Downward Outer Join" should be used. The VLDB property's behavior will be demonstrated using the following attribute and report. There is NO difference between the 'Preserve lookup table elements' options under the VLDB Properties editor vs. Choose the database instance and then open VLDB Properties. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". To change the parameter PARAM_QUERY_ROWSET_SIZE, add the lines below (adjusting for a number of rows to insert at a time) to ODBCConfig. See How to Edit VLDB Settings in. There are a number of them. Description. 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. x, select 'Project Documentation' from the Tools menu to. For steps, see the MicroStrategy Developer help. However, there is no governing for in-memory executions, including data blending which creates unnecessary risk to the stability and performance of the. Right-click a database instance and select Edit. MicroStrategy Advanced Reporting Guide provides comprehensive information on advanced topics for using the MicroStrategy query and reporting. VLDB properties can provide support for unique configurations. 3) In Joins, select Join Type. The “#n” code in Apply function syntax serves as placeholders for the MicroStrategy objects being passed to your database. Improved export customization: The Export to PDF dialog box has been added to allow formatting of PDF. Project-Level VLDB settings: Click to configure the analytical engine settings. You can connect to multiple projects on. 4. Community & Support Search Discussions Open A Case View My Cases1. You can determine the default options for each VLDB property for a database by performing the steps below. In MicroStrategy Developer versions prior to 9. The Use default inherited value option indicates the level that is active, while the SQL preview box. (In MicroStrategy Developer, navigate to VLDB Properties > MDX > MDX Cell Formatting. Open “Database instances” in the Categories menu, and click on “SQL Data warehouses”. ) User-defined. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. To be effective. Many of the VLDB properties control string syntax using SQL queries generated by the MicroStrategy SQL engine. KB11122: What is the “Downward Outer Join” VLDB property in MicroStrategy SQL Generation Engine? The downward outer join algorithm introduces a cost, in terms of performance and an inflated number of result rows, in exchange for improved data reliability. This is a Microstrategy way of handling database-specific preferences while generating the report SQL. One possible cause is some registry keys have some inconsistency. 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. A report is generated that displays all VLDB properties available at the level from which you accessed the VLDB Properties Editor. Report designers can then view the messages immediately without accessing the Intelligence Server machine. A given VLDB setting can support or. In the lower-right. The VLDB Properties Editor opens. 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. At the DBMS and database instance levels, it is set in the VLDB Properties Editor. In addition, this release introduces new features across the analytics, mobility, and security platforms—making it easier for users to build applications faster. Database instances for the project source are displayed. Use Case Statement option available in VLDB Properties, If your report contains any Custom Groups. The VLDB property's behavior will be demonstrated using the following attribute and report. See Template Editor. Clear the Use default inherited value check box. You can use MicroStrategy for different types of data analysis on a variety of data warehouse implementations. Here, we will use MicroStrategy Tutorial objects. The MicroStrategy platform provides VLDB drivers for all supported data warehouse platforms to generate optimized SQL that takes advantage of database specific functionality. Preview Feature: The FreeForm SQL Report Editor allows you to write your own queries to create reports. Project. Check the report SQL, and observe that permanent tables are still used as intermediate tables. This article describes what the evaluation ordering property is in MicroStrategy 9. The setting is applied. Choose Data > Configure Bulk Export. Choose Tools > Show Advanced Settings option if it is not already selected. 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. The VLDB property ‘Analytical Engine > ‘Filtering on String Values’ determines whether filters consider trailing spaces in attribute elements when filtering data in MicroStrategy. In the Results Set Row Limit field, type the limit. MicroStrategy Transaction Services and XQuery allow you to access. . This setting is called Join Across Datasets. VLDB properties are available at multiple levels so that SQL generated for one report can be manipulated separately from the SQL generated for another similar report. The recommended VLDB optimizations for Teradata 12. What are VLDB properties in MicroStrategy? 39. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. The properties are saved in different folders, as indicated in the previous list. It sets the general standards. ) From the Tools menu, select Show Advanced Settings. To the right of the Database connection area, click Modify. In the Grouping panel, right-click the grouping field to display horizontally, and select Grouping Properties. This is reflected in the checkbox “Use default inherited value for all VLDB properties”. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. The VLDB properties are grouped into different property sets, depending on their functionality: Viewing and Changing VLDB Properties. close menuNote: Changing the Analytical Engine VLDB property "Metric Level Determination" to the option "Include higher-level related attributes in metric level (deprecated)" bypasses the Analytical Engine normalization logic and also produces the expected report results. This information is available for each property in the VLDB Properties dialog box at each level. MicroStrategy Analytical Engine 9. Solutions available. " Save and close. This section focuses on the VLDB properties that are set at the metric and report level. x. You can use this setting on the following levels: To edit the setting, you must have "Use VLDB property editor. Clear the Use default inherited value check box. In MicroStrategy Developer, log in to a project. Report Level: Data -> VLDB Properties Unhide Parallel Options: Tools -> Show Advanced Settings Other VLDB settings that affect query generation. 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. Lets you identify attributes that include empty elements, which can then be ignored when. 2. The most likely cause for the difference in SQL is the fact that MicroStrategy 9. Project-Level VLDB settings: Click to configure the analytical engine settings. When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. Normally, MicroStrategy SQL Generation Engine attempts to combine metric calculations and attribute lookups into one pass of SQL. QUARTER_ID QUARTER_ID,KB14609: What is the 'Attribute Form Selection Option for Intermediate Pass' VLDB property in MicroStrategy 9. This. Pre- and Post-statements defined in the VLDB Properties of a project's primary warehouse database instance also apply to attribute element browsing requests, which are issued when browsing attribute elements in the data explorer in MicroStrategy Developer, or when a prompt must display a list of attribute elements. The default option is for aggregation calculations to ignore nulls and for scalar calculations to treat null values as zero. 1) From the Data menu, access the VLDB Properties option. Additional VLDB Settings. Microstrategy VLDB Properties; MicroStrategy VLDB properties with Hive;. x. x, "Use relational model" is selected by default. This issue has been addressed starting in MicroStrategy 9. Possible locations for VLDB optimizations in the query structure are listed below. Intermediate Table Type . When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. 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 >. Default VLDB properties are set according to the database type specified in the database instance. . From the Project Configuration screen, choose Database Instances, select the Database Instance you want to configure, and click VLDB Properties. You can use this setting on the following levels: Project level; Report level; Dossier visualization levelWhy MicroStrategy Why MicroStrategy; Customer Stories; Platform45+ [REAL-TIME] MicroStrategy Interview Questions & Answers - Free download as PDF File (. 1 and 10. You can choose to have the report display or hide the information described above, by selecting. This allows MicroStrategy to both properly support and take advantage of certain characteristics of each third-party data source. 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. 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. " Save and close. For information about accessing these properties, see the page reference for each property in the table below. They are exactly the same. '. To set these properties, open the report in the Report Editor or Report Viewer. Loading × Sorry to interruptGo to Data > VLDB Properties > Tables > Intermediate Table Type, change it to "Common table expression". 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. KB441418: Supplemental reference for installing Hotfix on MicroStrategy version 10. Modify the VLDB property you want to change. The image below shows how this hierarchy is populated on a report in. These tables can either be 'permanent' or 'true temporary'. Click the "VLDB Properties. Right-click on the report and click on the 'Edit' menu. Preview Feature: Create and edit reports with your favorite features including the Advanced Properties panel, View Filters, SQL View, and many more. 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. 201 Modifying VLDB properties at the report level. 199 Exercise 7. 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. Open the Workstation window. In Web: Click the MicroStrategy > Preferences. Execute the report and view the SQL:September 06, 2018. 8/7/2021. It has the following five options:What are VLDB properties? VLDB stands for Verly Large Data Base Properties. MicroStrategy application developers can further optimize SQL for their specific Oracle environment using these string insertion settings. Under Categories, expand Calculations, and select Attribute Join Type. 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 Intermediate Table Type property specifies what kinds of intermediate tables are used to execute the report. The Database instances - SQL Data warehouses pane displays. When the VLDB property Intermediate Table Type is set to "True Temporary Table", each pass results in a local temporary table. From the Tools menu, select Grouping. To create a last year transformation based on an expression. 5. Expand the 'Governing' folder and select 'SQL Time Out (Per Pass). In the Attribute Editor, on the Tools menu, select VLDB Properties. The recommended VLDB optimizations for Teradata 12 (and higher) are listed below. 3. 1 and 10. There is a method to change the default syntax for table and column names while generating MicroStrategy SQL during report execution in MicroStrategy by using VLDB properties. This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategy. Level dimensionality in a metric interacts differently with different features such as view filters, report filters, other metrics and certain VLDB properties. These settings are passed to the specific report/job VLDB properties only from the project primary database instance. 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. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. Use the temp table prefix in the (Very Large Database) VLDB properties window. 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. Report (or Intelligent Cube) In the Report Editor or Report Viewer, on the Data menu, select. Right-click on the project and select 'Configure project'. Parallel Query Execution. Additionally, the COALESCE function can be included in the SQL query. Use the Navigation pane to locate an Intelligent cube, incremental refresh report, project, or data source. MicroStrategy 9. Changing an option in one of the editors automatically reads the changes and is reflected in the other editor Certain VLDB properties use different default settings depending on which data source you are using. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. DATA ANALYSIS. For a data source, right-click it and choose Edit. This article explains how to migrate VLDB Select propertyset from an older metadata to a newly created metadata. For a project, right-click it and choose Advanced Properties. Report Caching Options, available to users with. MicroStrategy periodically updates the default settings as database vendors add new. Use this section to learn about the VLDB properties before modifying any default settings. Under VLDB Settings, navigate to the desired VLDB option. Upgrading Your Database Type Properties. 4. MDX cubes are also referred to as MDX cube sources. In this example, the raw ID is used. It can be enabled on project level: Open MicroStrategy Developer. 4. After the project information is processed, you are returned to MicroStrategy Developer. Other VLDB Properties are mentioned below. Under Project-Level VLDB Settings, click Configure. x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". Right-click a database instance and select Edit. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3. Accessing Database Instance VLDB Properties. The VLDB properties at the different levels work together to affect report results. Zillow has 471 homes for sale in Victoria BC. 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. 4. "The table below summarizes the Joins VLDB properties. This setting is used as an optimization for some databases which perform better when columns coming. For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. txt) or read online for free. To view VLDB properties. The four attribute join types available in the Report Data Options dialog box are the same as those in the VLDB Properties dialog box. This article explains the behavior of the commit level VLDB propertyThe MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. Database Instance Level This is the most common place to set VLDB Properties. 1, it is possible to identify specific attributes as having an incomplete lookup table by setting the “Preserve all final pass result elements” VLDB property within the attribute. 4. ) Microstrategy Desktop. In MicroStrategy 2020 Update 2, a new VLDB Property, Cartesian Join Governing, exists on the Project, Report, Dataset, and Visualization level. In the confirmation window that appears, click Yes. In MicroStrategy 10. Go to the 'Data' menu and select 'VLDB Properties'. Parallel Query Execution is an advanced property that is hidden by default. Only project configured with those setting is applicable for the case in this article. x. Choose Tools > VLDB Properties. After making the modification and restarting the Intelligence Server, the SQL Engine will disregard any changes made in the database instance. What are the various ways of incorporating security in Microstrategy? 40. To set these properties, open the report in the Report Editor or Report Viewer. Now your connection f. Follow the steps below to change the property. This VLDB setting can be changed at the Database instance, Report, and Metric levels. This guide discussesBy selecting this option, the Join Type VLDB property is assumed to be Join 92 and any other setting in Join Type is ignored. MicroStrategy Workstation lets you control how MicroStrategy Intelligence Server manages joins, metric calculations, query optimizations, and more for reports, documents, and dossiers. From the Tools menu, select Create VLDB Settings Report. 4. IntroductiontoMicroStrategy:EvaluationGuide 7 ©2016,MicroStrategyInc. Learn the basics of VLDB properties in MicroStrategy Developer, an advanced environment providing a complete range of analytical functionality designed to. To identify attributes that include empty elements, type the ID value for each attribute in the text field for this VLDB property. 4. Click on the upgrade button. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. For instructions on how to display this property, see Viewing and Changing Advanced VLDB Properties. (0 = time limit not enforced by this governing setting)The MicroStrategy Engine Essentials course explains the inner workings of the MicroStrategy Engine. 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. 10 Snowflake Derived Tables require non-standard Outer Join VLDB property settings. The solution is to backup old registry keys and re-generate default ones. The default setting for Db2 and Sub-Query Type is Option 4 – "Use temporary table, falling back to EXISTS for correlated subquery". VLDB_PROPERTY_VALUE: The value of the property, returned as a string. Metric-specific VLDB properties that can be set at the metric level include. This is reflected in the checkbox “Use default inherited value for all VLDB properties”. Accessing and Working with VLDB Properties. 4. However, each database instance is allowed to have its own VLDB property values. Then in the cube editor, go to the menu: Data > VLDB Properties to open the VLDB Properties window. To change the VLDB properties at any of the three levels, execute the following: Database Instance Level: Right-click on the Project name > Project Configuration. Change the VLDB setting . Enable. A given VLDB setting can support or. In MicroStrategy Developer, browse to an attribute, then right-click the attribute and select Edit. Go to Database instances > SQL Data Warehouses. Create a report with Year on the rows and Revenue on the columns. - On MicroStrategy Developer main toolbar, cick on ToolsProject Documentation - Follow the wizard selecting: (1) Application Objects (2) Advanced DefinitionIt is found in the Analytical Engine folder of the VLDB Properties (Metric) dialog box, pictured below. This article introduces a new VLDB property "Attribute Relationship Model" on Data Import Intelligent Cube dataset starting MicroStrategy 2021 Update 3 which allows Application Architect to quickly switch a Dataset from default "Attributes can be related through imported tables" mode to "Attributes can be related through 1:M relationships only" mode. Database Instance Level; Joins -> Cartesian Join Warning), either one or both of the two new VLDB properties, "Document Grids from Multiple Datasets" and "Remove Missing Units in Documents", are not shown: CAUSE. The VLDB Properties Editor opens. MicroStrategy specifies a default value for each database platform that will generate appropriate SQL for the database. You can manipulate things like SQL join types, SQL inserts,. This information is available for each property in the VLDB Properties dialog box at each level.