Without this option all reports would execute their SQL pass by pass in a sequential order over a single database connection. MSTR The key specified is the true key for the war. No set operators will be used. Using linear and seasonal regression for Revenue F. This is a known issue prior to MicroStrategy SQL Engine 9. This is a single-value function. Or embed self-service capabilities for users to visualize key drivers or what-if scenarios. The Security Role Editor opens. Choose one of the following: •. We're sorry. Attribute form. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Whenever users submit an element browse request or a report. Some databases, such as Oracle, do not support the ANSI 92 standard yet. MicroStrategy SQL Generation engine 10. MicroStrategy’s mobile support ensures flexible, real-time data exploration. Note: To create custom expression qualifications, the advanced qualification option must be enabled in the report designer's preferences in MicroStrategy Desktop 8. As you see, the sum of values in the quantity column in the table product is 7. Base Table Join for Template. They act as containers for non-standard SQL expressions that MicroStrategy does not support. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. 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. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. For raw ID, in the above example, SQL Date Format. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. The following settings are advanced properties which are. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. Go to Data > VLDB Properties > Joins > "Preserve all final pass result elements. Intelligence Server computes the new fact Trunc([Dollar Sales]) first and then uses the Sum function to sum the new fact for each region. Ans: MicroStrategy enables ad hoc analysis through an intuitive interface. x report for a specific attribute using an ApplySimple statement as one of its forms. select distinct a11. Although tables and indexes are the most important and commonly used schema objects, the database supports many other types of schema objects, the most. Example 1: Using SUMIF. The following three options are available for the VLDB property. For information on connecting to databases, see Connect to Databases. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 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. 2) Create Metric2 as the RunningSum of Metric1. ) User-defined. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. For Series this parameter is unused and defaults to 0. Default value changed for "Separate Count Distinct" VLDB setting for Impala 2. This flexibility is an important benefit of VLDB properties because it permits adjustment of many levels such as: REPORT - highest priority. Always consider to collect database statistics as the query execution plan is generated based on that. 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. 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. In MicroStrategy, a hint can be defined in VLDB properties to appear within a MicroStrategy-issued SQL statement. The hierarchy, or order of precedence, for VLDB properties is outlined in the. A report that shows sales for all the years and all the customer regions even if sales do not exist in the intersection of them can be achieved by the use. They are treated as 0s in the calculation. x introduces a third option to the VLDB Property "Drop Temp Table Method. The VLDB property, 'Additional Final Pass Option' is intended to override this behavior for single-pass reports. MicroStrategy’s OLAP functions are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. What do you. VLDB Function. Modify the SQL Date Format property to match either the MEMBER_NAME or raw ID. REGION_ID REGION_ID, max(a13. For example, if attribute Region is 'Central' then derived metric value should be 'Profit + Cost'. For example, the before and after SQL that is generated for a. Example. Since the report or template is not associated with a specific database instance, the primary. 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. It has two options: Disable Set Operator Optimization: SQL will be generated as in previous versions. This function is used to display the ranking of values in a list relative to the other values. Inputs for predictive metrics in Microstrategy; MSTR Passthough Functions; Applysimple, ApplyCompa. In MicroStrategy Developer, right-click a metric and select Edit. Database Instance. 3. To use previously defined in Db2 function in MicroStrategy, you can use the MicroStrategy built-in Apply (Pass-Through) Functions or use Freeform SQL. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. To access the parameters for the function, in the metric. Join common attributes (reduced) on both sides. After a report is run, we keep the connection open (DB connection timeout values apply). This calculation can be aggregated from the Employee level to the Region level. CAUSE: MicroStrategy can support multiple (more than 5) pre-statements to put in a report. For more information, see Simple vs. 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…. e. 2 metric aggregations will not be dimensionality aware. From MicroStrategy 9. x as the SQL hint VLDB property doesn't generate the desired SQL. By default, the Sum function will be used. Reuses redundant SQL. x, the only options were to drop tables or do nothing. ')"; [Net Weight. On the Freeform Sources tab, select Create Freeform SQL report. When MicroStrategy queries the data warehouse, the software determines which condition evaluates as true and then returns the value that the. 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 ApplySimple function is a single-value function. Ans: Statistics tables contain data on the MicroStrategy system’s usage and performance and are populated by all projects that are configured to log statistics. •. A list of security roles in the project source opens in the main Developer pane. For more details on enabling Feature Flags refer to What are the Feature Flag options and what do they accomplish in MicroStrategy Web 10. If not, the permanent table’s option is the default setting. Metric-specific VLDB properties in Microstrategy - Metric-specific VLDB properties in Microstrategy courses with reference manuals and examples pdf. Define the statistics and enterprise warehouse database. e. Go to Tools menu to enable the option “Show advanced settings” if it is not. Apply (Pass-Through) Functions MicroStrategy Apply. Specifies that SUM returns the sum of unique values. There is no VLDB setting associated with this option. For more information on the SUM() function, you can read this complete explanation of the SQL SUM() function. 0. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. This allows the FOJ to be rewritten to a different kind of join in the query. The downward outer join pass. Stream processing has been an active research field for more than 20 years, but it is now witnessing its prime time due to recent successful efforts by the. x attempts to combine metric calculations and attribute lookups into one pass of SQL. . If the option for multiple passes is selected, all metric calculations will be performed in separate passes. The default syntax can be modified by using 'Column Pattern' VLDB property. The first four statement VLDB properties, each can contain single SQL statement. , a temporary table is created but not referenced in a later pass; Reuses redundant SQL passesKB37567: MySQL table specific SQL hints cannot be used in reports against MicroStrategy 9. The Apply functions are not meant to take. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. To modify the VLDB Properties at the report level edit datamart report and select Data > VLDB Properties…. x and 10. As you type, matching objects are displayed in a drop-down. Returns the date of the first day of the month in which date or timestamp occurs. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. Sum . The Apply functions are not meant to take the place of the standard MicroStrategy functions. Metric definition: Sum (IF (Employee@ID In (1,2,4,5),Revenue,0)){~+} This is good as a quick solution, since. They can also help you take more advantage of the data. Group by column. These functions are collectively called “ordered analytical functions” in Teradata, and they provide significant analytical capabilities for many business analysis queries. We use MicroStrategy Tutorial objects to create this example. Example. For example, the SQL SELECT statement below returns the combined total salary of unique salary values where the salary is above $25,000 / year. How to avoid: By default, MicroStrategy uses database connection caching. For example, the SQL SELECT statement below returns the combined total salary of unique salary values where the salary is above $25,000 / year. This procedure assumes you are already working with a metric in the Metric Editor. Grouping. The New Grid dialog box opens. This information is available for each property in the VLDB Properties dialog box at each level. The Table Creation Type property tells the SQL Engine whether to create a table implicitly or explicitly. Ans: MicroStrategy handles metadata by centralizing it within its Intelligence. This will grab the 25 records quickly, but because most databases do not store table data in any particular order, every report execution would get a different set of. However, the SQL used to execute the report can still be viewed and obtained. The attribute uses a CASE statement to replace NULL values with -999. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. MONTH_ID IN (#E1). In general, a user specifies a list of conditions and corresponding return values. This is an OLAP function. The MicroStrategy Engine includes three built-in functions to handle conditional expressions: IF(), Case() and CaseV(). Pass-through expressions, also called Apply functions, provide access to special functions or syntactic constructs that are not standard in MicroStrategy, but can be obtained through the relational database. There are two options for this property: CREATE and INSERT statements are supported. Determines how distinct counts of values are retrieved from partitioned tables. If the MEMBER_NAME is 03/05/2007, the SQL Date Format should be mm/dd/yyyy. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. 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. Create a new Report: Add Quarter, Customer, and Profit to the template. ) will apply. This allows SQL to be run after the report execution, and is not tied to the subscription. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. 0. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. You can click an object or continue to type. If no ordering is specified, the result of some window functions (e. Also notice that the MovingSum values for the dates 1/1/2000 and 1/2/2000 do not include data before 1/1/2000 in its calculation. This setting can reduce the number of SQL passes generated by MicroStrategy. The report results after making this change can be seen below. 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. DAY_DATE DAY_DATE, a12. Specifies that SUM returns the sum of unique values. 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. x and 10. ; Distinct is a TRUE/FALSE parameter that allows you to. This setting is used as an optimization for some databases which perform better when columns coming from. SQL Syntax for Ordered Analytic Functions: Moving average example: select a11. g. x. This VLDB setting is located in metric editors, as shown below. Sum_Range= optional argument to be. Navigate to Tools > Advanced Settings > VLDB Properties to open the VLDB properties editor. To provide a reasonable level of generality, the feature is based on a 'pattern and arguments' scheme. Write VLDB properties? VLDB stands for Very Large Data Base Properties. One of the options under Analytical Engine folder is called "Metric Level Determination. " In MicroStrategy SQL Generation Engine 8. It is possible to disable the warning by setting ansi_warnings off but this has other effects, e. In such a case, Report Pre and Post Statements from all database instances will be ignored. How to change the syntax is described in detail by using examples. 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. MicroStrategy may not be able to provide additional code on this matter even though. 0, a VLDB property is available to control. 4. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. The user should locate the VLDB. The possible values for this VLDB property are: • Permanent table46. MicroStrategy’s OLAP functions are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. 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. Viewing and Changing VLDB Properties. Create a formula in it of. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. Each of the functions in this category substitutes for one of the function types mentioned above and can be used wherever that type is used. For more information regarding post statements defined at the report level, refer to the following Technical Note: KB14618:. . Apply Comparison – Uses comparison. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. 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. Apply (Pass-Through) Functions MicroStrategy Apply Functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various Relational. Single-value functions can be used to create. ApplyAgg – Uses aggregate functions such as Sum, Max, and so on. VLDB Settings. Most databases expect only one statement per SQLExecDirect. 0 or above, to pick up the fix, enable project level setting "Data Engine Version" to 11. This is a single-value function. If parentheses are required in the database syntax, it is the user's responsibility to provide them, e. Double-click the security role you want to assign to the user or group. The VLDB settings report now displays all the default settings for the data source. We have focused on the features that have been developed specifically to support and enhance the SQL Server integration. The VLDB property's behavior will be demonstrated using the following attribute and report. The VLDB Properties Editor opens. 4. Attribute form expressions must be rendered into SQL and cannot use any MicroStrategy functions specific to the Analytical Engine. This calculation can be aggregated from the Employee level to the Region level. If you choose Temp Table Join. Depending on your MicroStrategy product and licensing, this function may not be available. #. The RANK function is closely related to other OLAP functions. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. 1. Developers can retrieve the report SQL statement when running a report with the following customization: Launch the Web Customization Editor. Governor. Metric with an IF Function. The First option, 'CREATE and. The example below outlines how to create a Sum custom subtotal that only totals the last two metric values . [TOT_DOLLAR_SALES]) AS Revenue into [ZZEA00] from. Loading × Sorry to interruptIn the Functions pane, hover over the If or Case function and click Edit. Define the statistics and enterprise warehouse database. g. CAUSE: By checking the SQL statements of the report, there is no "sum" or "group by" statement. For example, if a ranking window function is used, the rank is computed with respect to the specified order. "Firma", SUM. Report as Filter inherits its parent report's VLDB setting instead of using its own. If you are not, do one of the following: 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. 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. 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. By default a report with the Category attribute and the Revenue metric would generate the SQL statement as shown below. 6. Need to find the sum of the bill amount for particular orders. The formula of a simple metric is based on group functions (such as sum or average). 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. The First option, 'CREATE and. The formula of a simple metric is based on group functions (such as sum or average). Qualify on the attribute form that you want to compare (presumably the Year ID), and then in the Operator section, change the dropdown from its default 'Value' to 'Custom'. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. The impact is limited to MicroStrategy Command Manager 9. compound metrics. x. 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. A base formula does not have dimensionality (see. Browse to the filter you want to convert. Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. 5. •. Criteria= the condition. The two metrics filters are simple attribute qualifications which are allowed under Global Optimization. expression. CAUSE: The attribute form used for the 'group by' clause of the SQL generated is not an ID form. ; Distinct is a TRUE/FALSE parameter that allows you to. 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. Multiple passes are generated only when necessary to resolve all the metric definitions. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. AS CUSTOMER_ID, a11. 68K KB325314: In MicroStrategy 9. Below is the supported OLAP functions by MicroStrategy with associated SQL pattern. In general, ApplySimple can be used to create the following objects: •. Note how adding an unrelated dataset unexpectedly changes the data returned by M02=Sum(Case): Cause This is a known issue in MicroStrategy 2019. 7. x. Set up the Enterprise Manager. TEMPLATE. For use cases, examples, sample code, and other information on every VLDB property. The resulting SQL will contain just the Metric Alias. pandas. [CATEGORY_ID] AS CATEGORY_ID, sum(a11. This section includes the following. To do this, the "Preserve all final pass result elements" VLDB property must be set at both attribute and report level. Aggregate functions and subqueries are not. However, the SQL used to execute the report can still be viewed and obtained. For details on each of these. FROM OrderDetails WHERE ProdictId = 11; Try it Yourself » Use an Alias Give the summarized column a name by using the AS keyword. e ('Call [SP]') it does not. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. Community & Support Search Discussions Open A Case View My CasesAns: Statistics tables contain data on the MicroStrategy system’s usage and performance and are populated by all projects that are configured to log statistics. Please note that the changes to this object will not be visible until the cube. Create the statistics database instance. These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. Normally, MicroStrategy SQL Generation Engine attempts to combine metric calculations and attribute lookups into one pass of SQL. You can use them in many different capacities, which include, creating or modifying both schema and user objects. select distinct a11. The attribute uses a CASE statement to replace NULL values with -999. on how division by zero is handled and can cause failures when your queries use features like indexed views, computed columns or XML methods. Statement in VLDB Properties i. This article describes an issue where attribute elements that include trailing spaces are not returned as separate attribute elements when Filtering on the String Values VLDB property is set to "Do not trim trailing space" in MicroStrategy 10. This article describes how the element browsing pre-post sql statements work in MicroStrategyFunctions Reference. The VLDB property, 'Additional Final Pass Option' is intended to override this behavior for single-pass reports. The window size is a parameter which tells the function how many of the values should be included in the calculation. Using Apply functions is recommended only when corresponding functionality does not exist in MicroStrategy. The database was created with files stored directly in Azure blob storage , using a Premium Storage. Helps optimize custom group banding when using the Count Banding method. 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. Community & Support Search Discussions Open A Case View My CasesVLDB is an acronym for “Very Large DataBase”. MicroStrategy value prompts do not allow multiple values. The Moving Sum function returns a cumulative total of values based on a specified window size. Generate report SQL (see the table below under ‘Without Setting’). These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. Number of Views 822. Attribute. 82K KB11125: How to control the join order of metrics in the final pass when using the "Do. Help your customers get more out of the app experience with an engaging AI assistant that provides automatic answers or outputs in real time. The database was created on a SQL Server VM in Azure by loading data from text files in Azure Blob Storage, using PolyBase . This knowledge base article describes an issue in MicroStrategy 10. This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Governor. 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. Each conditional metric contains a copy of employee list (in an IF statement) Employee list filter is moved to a separate metric (Flag metric) Employee list filter is moved to a Filter object. Intermediate Table Type. 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 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. This article explains the behavior of the commit level VLDB property35. When you need to use an Apply function, MicroStrategy encourages you to submit an enhancement request for inclusion of the desired feature in a future product release. Returns a date or timestamp plus an offset (+ or -) n days. The following steps describes how to create such derived metric. Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. The ApplyAgg function is used to define simple metrics or facts by using database-specific, group-value functions. By default a report with the Category attribute and the Revenue metric would generate the SQL statement as shown below. This article does contain a solution. 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. The properties are saved in different folders, as indicated in the previous list. Specify a name and location for the new security filter and click Save. 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. 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. Examples of SQL SUM() Given below are the examples of SQL SUM(): Example #1 – Using a single column. IMPORTANT: If Report Pre and Post Statements are defined in report or template level VLDB Properties, these will override the settings in database instances. 8 and up . The CaseV function takes a numeric value M1 as input and compares it to another numeric value V1. In the VLDB Properties window, expand the folder called 'Tables'Normally, MicroStrategy SQL Generation Engine 9. This section focuses on the VLDB properties that are set at the metric and report level. Step 2: Enabling Parameterized Queries (for supported databases) Step 3: Define Secure Freeform SQL Reports (for supported and unsupported databases) Escaping special characters in input data is. Interact with the engaged MicroStrategy Community to get answers to all your. Column aliases allow you to specify a more appropriate data type that can help avoid errors in your SQL. SQL. Right-click on the report and click on the 'Edit' menu. VLDB Data Type . The Profit metric is a simple sum of the Profit fact. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. For information on connecting to databases, see Connect to Databases. This version of the product is no longer supported in accordance with MicroStrategy's support lifecycle. g. Explain how MicroStrategy handles metadata. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. As you type, matching objects are displayed in a drop-down. The above example would not be valid with multiple months in the answer because the >= expects single values for its operands. The syntax for the CaseV. 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. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. Place attributes Country and Distribution Center on report template, and the above metric either on report template, or in Report Objects window if you have an OLAP license. By design, however, MicroStrategy SQL Generation Engine 8. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB. Or, the MEMBER_NAME might be March 5, 2007, in which case the SQL Date Format would be mmmm d, yyyy. Create a New Subtotal, right click the Sum function to open Sum Parameters, and then set the Distinct value as True. This query does not return all desired elements of category from the Data Warehouse. For Compound Profit to be dynamically aggregated correctly, you change the dynamic aggregation function to Sum. For example, if attribute Region is 'Central' then derived metric value should be 'Profit + Cost'. It is, consequently, displaying a total which is. Viewing and Changing VLDB Properties. Calculating a Compound Metric. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. (0 = time limit not enforced by this governing setting)MicroStrategy has a VLDB (Very Large Database) setting that can be configured to indicate the underlying database software does not support Full Outer Join operation. Some databases do not support implicit creation, so this is a database-specific setting. Expand the 'Administration' Icon, and select the Database Instance Manager. However, MicroStrategy cannot guarantee an optimal ordering of tables unless there is at least one report level metric. September 18, 2018. If you are editing the If function, use the values in step 7. Case. If all conditions are false, a default value is returned. For example, in the following formula - MovingSum (Revenue, 3) - only the previous three values are to be included in the. To force a Null check for the second case, use the Function 'NullToZero' either in the metric or Fact Editor. In order to do this a VLDB property exists to disable the data blending feature. 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. Choose the database instance and then open VLDB Properties. For information about accessing these properties, see the page reference for each property in the table below. IMPORTANT: If Report Pre and Post Statements are defined in report or template level VLDB Properties, these will override the settings in database instances.