This section includes the following. As a result the report throws. As you see, the sum of values in the quantity column in the table product is 7. MicroStrategy uses different defaults for the join type based on the database you are. Example: The SQL below is from a report that can use parallel execution. This is an OLAP function. These are called pass-through functions because Microstrategy does not check the actual SQL construct and dumps it as is on the database. This sometimes produces SQL that is expensive to run on the database, particularly if multiple attribute lookup tables are combined using cross joins. If you choose Temp Table Join. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. In the examples in this article, we will be using a 12 TB database, appropriately named VLDB01. [M1]:. However, the expression '' alone will not check for NULLs although the Very Large Database (VLDB) setting is activated. A given VLDB setting can support or. Some of these limitations are described in the following article: KB30257 - "Limitations of "derived table" intermediate table type VLDB setting in MicroStrategy SQL Engine" Another limitation of this setting is using multisource SQL. For example, the SQL SELECT statement below returns the combined total salary of unique salary values where the salary is above $25,000 / year. The CaseV function takes a numeric value M1 as input and compares it to another numeric value V1. expression. VLDB properties can force a report filter to be applied to the final pass of SQL As seen in the scenario above, three rows are returned when the report filter is set to 2010 and 2011. Multiple passes are generated only when necessary to resolve all the metric definitions. The post-execution SQL that was available in Narrowcast can be replaced by implementing post-report SQL VLDB properties. Open MicroStrategy Developer. Sum . Using linear and seasonal regression for Revenue F. So when the value was changed to 'Check for NULL in all queries' at the report level, the MicroStrategy SQL Generation Engine issued a NULL validation for the metric. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformYou can use the SQL DISTINCT clause within the SQL SUM function. In general, a user specifies a list of conditions and corresponding return values. To set these properties, open the report in the Report Editor or Report Viewer. Most of MicroStrategy’s OLAP functions (24 out of 31) are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. The VLDB setting "Do not do downward outer join for databases that support full outer join" is appropriate in the following situations: The following steps provide an overview for configuring secure Freeform SQL text prompts: Step 1: Identify Database Support for Parameterized Queries. The VLDB property's behavior will be demonstrated using the following attribute and report. Beginning with MicroStrategy SQL Engine 9. MONTH_ID IN (#E1). Pass-through expressions, also called Apply functions, allow use of special functions or syntactic constructs beyond what MicroStrategy can create on its own, but can be obtained through the relational database. Axis for the function to be applied on. Several additional VLDB properties are introduced with MicroStrategy 9. CAUSE: MicroStrategy can support multiple (more than 5) pre-statements to put in a report. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. 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. The following steps describes how to create such derived metric. Note that the SUM() function ignores NULL values. There is no VLDB setting associated with this option. Passes that hit the same fact table across different elements of a custom group are merged provided that they satisfy certain conditions. In MicroStrategy SQL Engine, a VLDB setting "Custom Group Interaction with Report Filter" exists to manage different situations in which a Custom Group interacts with the report filter. 1. Multipass SQL statements in Freeform SQL are not supported in Microstrategy. Attribute level: Select the desired join behavior for this 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. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. Pass 1. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. Sum <Distinct, FactID, UseLookupForAttributes>(Argument)Where: Argument is an attribute, fact, or metric representing a list of numbers. No set operators will be used. Key distinctions of the RANK function are that it requires an order by clause and does not support a window clause. g. Right-click on the report and click on the 'Edit' menu. When they do appear, report designers have some degree of control over the subquery syntax using the Very Large Data Base (VLDB. The attribute uses a CASE statement to replace NULL values with -999. One of the options under Analytical Engine folder is called "Metric Level Determination. Returns a date or timestamp plus an offset (+ or -) n days. For more information, see Simple vs. Tables − They simply represent data in a tabular form (columns and rows). Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. Syntax. Watch free 3-5 minutes tutorial videos, with subtitles available in 9 languages, to build product fluency! Start learning. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Join common attributes (reduced) on both sides. Functions can be pushed down to. July 05, 2018 Apply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are. The SQL SUM () Function. The hierarchy, or order of precedence, for VLDB properties is outlined in the. e. In general, a user specifies a list of conditions and corresponding return values. CREATE and INSERT statements are not supported. Although transformations can be applied to any attribute hierarchy, the Time hierarchy is used most often. 4. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. This article describes how the element browsing pre-post sql statements work in MicroStrategyFunctions Reference. The Profit metric is a simple sum of the Profit fact. In order to do this a VLDB property exists to disable the data blending feature. Inputs for predictive metrics in Microstrategy; MSTR Passthough Functions; Applysimple, ApplyCompa. Governor. a temp table is created but not referenced in a later pass. 8 and up . This knowledge base article describes an issue in MicroStrategy 10. Go to Tools menu to enable the option “Show advanced settings” if it is not. Microstrategy fetches the list of values to be displayed in an Attribute Element Prompt by executing two passes of SQL as seen below: Pass 0. Help your customers get more out of the app experience with an engaging AI assistant that provides automatic answers or outputs in real time. In these cases, the MicroStrategy SQL Engine uses the value set in the VLDB setting, 'Fallback Table Type'. This document introduces how to apply conditional logic on a derived metric according to attribute form whose type is character. Intermediate Table Type. Case. In MicroStrategy, a hint can be defined in VLDB properties to appear within a MicroStrategy-issued SQL statement. You can apply transformations to simple metrics but not for compound metrics. In the Form expression pane, place the cursor to the right of [CUST_LAST_NAME] and type + ", " +. Simple metrics always contain at least one aggregate function, such as sum or average, applied to a fact. That is, we can define the order in which operations are performed, optimization level, joins intermediate steps, Hints, and many more things that even go into advanced complexity. This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategyIt has two options: Disable Set Operator Optimization: SQL will be generated as in previous versions. This article describes how to use wildcards to display temporary table names in pre/post statements. When this subtotal line is enabled, the Analytical Engine looks to the 'Total subtotal function' to decide which Subtotal object in the metadata to use when evaluating the subtotal. The hierarchy, or order of precedence, for VLDB properties is outlined in the. IMPORTANT: If Report Pre and Post Statements are defined in report or template level VLDB Properties, these will override the settings in database instances. (For step by step instructions on creating a new plug-in, please navigate to Home > Web SDK > Customizing MicroStrategy Web > Web Customization Editor. Base Table Join for Template. Types of variables Before going into the details of the types of Apply Functions , I will point out that these functions require certain variables to be passed as parameters. This setting also applies to the use of security filters for creating an element cache. To use previously defined in Db2 function in MicroStrategy, you can use the MicroStrategy built-in Apply (Pass-Through) Functions or use Freeform SQL. Unless the defaults are changed, the function ranks the values in ascending order by the value of the metric, and the rank is an integer. A comment that passes instructions to a database optimizer about choosing an execution plan for a given SQL statement. The MicroStrategy Engine is aware that Oracle supports the Rank function, so the ranking will be done by the database rather than the MicroStrategy Analytical Engine. Instead, they are intended to enhance the MicroStrategy product by taking advantage of what the RDBMS platforms can offer. The functionality of Apply functions is provided by wrapping the expression, as a string, inside a dedicated (Apply) function call. Rank. Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. This displays the descriptive information of each default VLDB property setting in the VLDB settings report. TEMPLATE. sum. For more details on this latter scenario, consult the following MicroStrategy Knowledge Base. . These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. REGION_ID REGION_ID, max(a13. Functions in MicroStrategy are powerful tools used in expressions to define MicroStrategy objects and initiate complex user-selected calculations. For all other valid Intermediate Table Type VLDB settings, the SQL does not reflect the values set for these properties. DataFrame. Given the data table with order numbers and the bill amount. 11: enable the Feature Flag "Defect fixes that may impact Data, SQL, MDX, CSI" within the Web Preferences -> Project Defaults. VLDB Settings. Expand the 'Administration' Icon, and select the Database Instance Manager. Summary: To view a summary of the system components that contain VLDB properties for a given report, select one of the system-level folders displayed under the VLDB Settings headings to view a summary of the properties listed for that folder. ADDITIONAL INFORMATION:. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. To configure:-. SQL Global Optimization. This occurs when the data type of the. The database was created with files stored directly in Azure blob storage , using a Premium Storage. 1) Create Metric 1 which is the sum of the fact that is to be in the columns. The second step is to compute the sum. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. In general, a user specifies a list of conditions and corresponding return values. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. The window size is a parameter which tells the function how many of the values should be included in the calculation. Beginning with MicroStrategy 9. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. This article describes how MicroStrategy uses subqueries and how the options of the "Sub Query Type" VLDB property control the SQL syntax used. The location of each property in the CREATE TABLE statement is given below. Aggregate functions and subqueries are not. Group by column. 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. What do you. You can click an object or continue to type. ApplyOLAP – Uses OLAP functions such as Rank, Ntile, and so on. Attribute form. Apply functions: These functions provide access to functions and syntactic constructs that are not standard in MicroStrategy but are offered by various relational database management system (RDBMS) platforms. x as the SQL hint VLDB property doesn't generate the desired SQL. Although tables and indexes are the most important and commonly used schema objects, the database supports many other types of schema objects, the most. These functions are collectively called “ordered analytical functions” in Teradata, and they provide significant analytical capabilities for many business analysis queries. Splitting the fraction: Numerator: Sum (VOL) {~} Denominator: Max ( ApplySimple ("replace (#0, ',', '. Action If the CASE expression has only one branch -- i. Enable Set Operator Optimization (if supported by database and [Sub Query Type]): Use set operators when possible. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. Create a metric with the ApplySimple statement below as its definition and name it. This is true whether the null checking is written into the metric formula using the MicroStrategy function NullToZero(My_Fact), or using a database pass-through function such as ApplySimple("NVL(#0, 0)", My_Fact) for Oracle. Since the report or template is not associated with a specific database instance, the primary. In general, a user specifies a list of conditions and corresponding return values. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. 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. . 5, multi-source reports inherit the Report Pre/Post Statement VLDB setting only from…Normally, MicroStrategy SQL Generation Engine 9. , row number) is non-deterministic. To modify the VLDB Properties at the database instance level right-click on the data warehouse database instance in the Database Instance Manager and select VLDB Properties…. 9 / 10. Ans: MicroStrategy handles metadata by centralizing it within its Intelligence. This is a known issue prior to MicroStrategy SQL Engine 9. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. 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. If the report uses only inner joins, then the only thing that changes is the table order. g. (For information on object levels, see Order of Precedence . MicroStrategy SQL Generation engine 10. Metric-specific VLDB properties in Microstrategy - Metric-specific VLDB properties in Microstrategy courses with reference manuals and examples pdf. . `Temporary view` intermediate table type VLDB settings is not applied in MicroStrategy when using Warehouse Partition Mapping Table. 0 and higher). Generate report SQL (see the table below under ‘Without Setting’). Most databases expect only one statement per SQLExecDirect. For example, if attribute Region is 'Central' then derived metric value should be 'Profit + Cost'. Metric definition: Sum (IF (Employee@ID In (1,2,4,5),Revenue,0)){~+} This is good as a quick solution, since. The first four statement VLDB properties,. 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. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. OR, to convert an existing filter into a security filter, click Import. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. Examples of SQL SUM() Given below are the examples of SQL SUM(): Example #1 – Using a single column. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. Select the Members tab. VLDB Data Type . If you are upgrading to MicroStrategy 10. Select the Members tab. Apply Functions provide the capability for MicroStrategy customers to leverage functions specific to RDBMS but not standard in MicroStrategy. The example below outlines how to create a Sum custom subtotal that only totals the last two metric values . x includes a VLDB property, 'CREATE and INSERT Support,' under the Tables folder, at the database instance level. How to avoid: By default, MicroStrategy uses database connection caching. KB11125: How to control the join order of metrics in the final pass when using the "Do not do downward outer join" VLDB setting in MicroStrategy SQL Generation Engine. Loading × Sorry to interruptIn the Functions pane, hover over the If or Case function and click Edit. This article explains the behavior of the commit level VLDB property35. Let us create one simple table named numbers and store the. In general, a user specifies a list of conditions and corresponding return values. The VLDB property, 'Additional Final Pass Option' is intended to override this behavior for single-pass reports. By default, the metrics Compound Profit and Profit Margin do not use a dynamic aggregation function. Returns the sum of all numbers in a list of values. x. Each of the functions in this category substitutes for one of the function types mentioned above and can be used wherever that type is. There is no VLDB setting associated with this option. This information is available for each property in the VLDB Properties dialog box at each level. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. This VLDB setting is located in the 'Indexing' folder and has the following options:The following example demonstrates the use of the VLDB property "Compute Non-Agg before/after OLAP functions (e. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Example: Create a new custom subtotal object. While this code may apply to other releases directly, MicroStrategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. 4. 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. IMPORTANT: If Report Pre and Post Statements are defined in report or template level VLDB Properties, these will override the settings in database instances. Need to find the sum of the bill amount for particular orders. The VLDB property "Attribute ID Constraint" is used during creation of intermediate tables to specify whether the attribute ID columns in those tables will or will not allow null values, or to use other constraints allowed in the warehouse's SQL implementation. x and 10. 3. 'For the Databases listed, the minimum function is utilized in SQL to emulate the data that would be returned when utilizing the LEAST function on the particular database providing an incorrect data result. 5. The structure of the second dataset does not matter so much; we add the "CITY_MNTH_SLS" table. It is possible to disable the warning by setting ansi_warnings off but this has other effects, e. [M1]:. ACTION: This is addressed MicroStrategy 11. Select the Security Filters tab. Example: The SQL below is from a report that can use parallel execution. How to confirm if the parameterized queries feature is on or off? Edit your DB instance from Developer path Administrator -> Configuration Managers -> Database Instances , or the DB role from Web data import page Add External Data -> Oracle ->Any. Create the statistics database instance. VLDB Insert. CAUSE: By checking the SQL statements of the report, there is no "sum" or "group by" statement. For information on connecting to databases, see Connect to Databases. Attribute form expressions must be rendered into SQL and cannot use any MicroStrategy functions specific to the Analytical Engine. 3. Using Apply functions is recommended only when corresponding functionality does not exist in MicroStrategy. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. This document will use the MicroStrategy Tutorial project with a warehouse in SQL Server to demonstrate the concept: Create a numeric value prompt and name it P1. Tutorial project is used here. The default syntax can be modified by using 'Column Pattern' VLDB property. A VLDB database. This article describes a scenario where SQL will be generated with intermediate tables regardless of the intermediate table type VLDB property Many of MicroStrategy’s OLAP functions are calculated via SQL in SAP HANA rather than in the MicroStrategy analytical engine. To simplify the explanation, this function is used to apply non-standard SQL expressions that MicroStrategy does not support or does not support. 4. If no ordering is specified, the result of some window functions (e. For information on connecting to databases, see Connect to Databases. x mixed case columns names for a DB2 database by default have SQL generated with quote characters enclosing the name . Helps optimize custom group banding when using the Count Banding method. If two users with different security filters run the same report, they may get different results. g. x. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. STEPS TO REPRODUCE: In MicroStrategy Tutorial, create a report containing Country in the rows and End On Hand metric (mapped to a partitioned fact table) in the columns. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. #. To change the default dynamic aggregation function. A list of security roles in the project source opens in the main Developer pane. Database Instance. When the 'Use inherited value' flag was checked for the setting at the report level, it went back to the higher object with an unchecked flag (the metric level) and used that. 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. Beginning with MicroStrategy SQL Engine 9. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. Reuses redundant SQL. Define the statistics and enterprise warehouse database. MSTR The key specified is the true key for the war. However after re-migrating the freeform SQL report to the target environment, the report still shows the results with the total subtotal function and dynamic. The Apply functions are not meant to take. In the event of a code change in future builds, MicroStrategy may not be able to provide additional code on this matter even though this customization is provided. Content In order to create a metric in MicroStrategy Visual Insight to filter on a specific attribute, a Case statement function can be used to get the designed results. SELECT SUM(DISTINCT salary) AS "Total Salary" FROM employees WHERE salary > 25000; If there were two salaries of. For information about accessing these properties, see the page reference for each property in the table below. This article describes how to modify MicroStrategy to remove coalesce functionsOpen the VLDB Properties Editor: . In such a case, Report Pre and Post Statements from all database instances will be ignored. MicroStrategy SQL Generation Engine will not automatically add parentheses around the list. expression. The SUM () function returns the total sum of a numeric column. REGION_ID REGION_ID, max(a13. This function is used to display the ranking of values in a list relative to the other values. This article explains how the applycomparison function works in MicroStrategy[IM001:0: on SQLHANDLE] [Microsoft][ODBC Driver Manager] Driver does not support this function. The SUM () function adds all values from the quantity column and returns the total as the result of the function. Example include ApplySimple, ApplyComparison, etc. Choose one of the following: •. x database and leads to different SQL. This calculation can be aggregated from the Employee level to the Region level. Double-click the security role you want to assign to the user or group. This means that the MicroStrategy internal OLAP function 'MovingSum' will be performed on the Sum() aggregation, sorted by the month ID with a window size of 2 (2 last values). Apply functions: These functions provide access to functions and syntactic constructs that are not standard in MicroStrategy but are offered by various relational database. To see an example that uses this technique, see Estimating dynamic aggregation values with different aggregation functions. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. 1 - 10. Assuming that users have two database instances, one for the. 0, a VLDB property is available to control. Transformations − They are the data transformation features used for time-series based analysis of the data. The ApplyAggregate, or ApplyAgg() function, can be used to bypass the SQL parser with mathematical functions. "Firma", SUM. Apply (Pass-Through) Functions MicroStrategy Apply. Follow the steps below to change the property. Note how adding an unrelated dataset unexpectedly changes the data returned by M02=Sum(Case): Cause This is a known issue in MicroStrategy 2019. Create the statistics database instance. PROJECT. The Create New Form Expression dialog box opens. The user should locate the last <Setting> XML entry in the file similar to the following entries:<Setting>Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. A list of security roles in the project source opens in the main Developer pane. Depending on your MicroStrategy product and licensing, this function may not be available. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. The syntax for the If function is IF (Condition, TrueResult, FalseResult) where:Explanation. How to change the syntax is described in detail by using examples. Without this option all reports would execute their SQL pass by pass in a sequential order over a single database connection. Wherever you can define an expression, you can use a function. In MicroStrategy Developer, choose File > New > Report. This is an OLAP function. Navigate to Tools > Advanced Settings > VLDB Properties to open the VLDB properties editor. Create a metric with M03 = MonthStartDate (CurrentDate). Therefore, this setting only works when the 'Intermediate Table Index' VLDB setting is set to one of the following options: The following example demonstrates the use of the VLDB property "Compute Non-Agg before/after OLAP functions (e. Create another filter F2 with the same parameters as F1, but do not copy or use the same filter, as the optimization engine will otherwise not generate a duplicate pass. Helps optimize custom group banding when using the Count Banding method. Aggregate functions and subqueries are not. tion. This setting can substantially reduce the number of SQL passes generated by MicroStrategy. Select the filter or prompt to apply to the metric using one of the following methods: To type the filter or prompt directly, begin typing the name of the filter or prompt in the field in the Condition area. If the ApplySimple statement is in fact included as the. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. To use an element list prompt with Freeform SQL, the following conditions must be met: The prompt must be based on an attribute in the project's primary schema (a Freeform SQL or. The first is to enable the SQL Hint VLDB property and include a TOP (or BOTTOM) clause. Range: The range of cells which included the criteria; Criteria: The condition that must be satisfied; Sum range: The range of cells to add if the condition is satisfied. Tell the usage of command manager? The command manager is used to save the text commands which can be executed as scripts. select a11. x and higher. Returns the sum of all numbers in a list of values. The SQL hint VLDB property places the desired custom SQL inbetween the select keyword and the columns in SQL This article notes how to setup Ranking for metrics that do not return data for all attribute elements Apply functions: These functions provide access to functions and syntactic constructs that are not standard in MicroStrategy but are offered by various relational database management system (RDBMS) platforms. You can re-use the same formula in multiple metric definitions. x includes a VLDB property, 'CREATE and INSERT Support,' under the Tables folder, at the database instance level. The "Grouping" property has six possible settings, of which four specify non-aggregating behavior: Beginning (fact) Ending (fact)This issue has been classified as a defect by MicroStrategy. Users can explore, filter, and visualize data with drag-and-drop functionality. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformExecute the report and see the result below. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. Enter the values to use as arguments. Syntax. •. 3. on how division by zero is handled and can cause failures when your queries use features like indexed views, computed columns or XML methods. It does not apply to situations where index creation occurs before insertion of data. The report results after making this change can be seen below. Normally, MicroStrategy SQL Generation Engine attempts to combine metric calculations and attribute lookups into one pass of SQL. Modify the VLDB property you want to change. To configure:-. When a Freeform SQL report's query is submitted to the database, the entire query text is sent using a single ODBC SQLExecDirect call. Rank) calculated in Analytical Engine" found under the 'Metrics' folder in the list of VLDB properties.