However, MicroStrategy cannot guarantee an optimal ordering of tables unless there is at least one report level metric. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. If all conditions are false, a default value is returned. The First option, 'CREATE and. 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. Use of M03 in Microsoft SQL Server 2000 would result in DATEADD (DD, (1 - DAY (GetDate ())), GetDate ()). The first is to enable the SQL Hint VLDB property and include a TOP (or BOTTOM) clause. There is no VLDB setting associated with this option. Create the statistics database instance. Multiple passes are generated only when necessary to resolve all the metric definitions. Note: There is an additional "Do not do downward outer join" setting that automatically orders the metrics based on dimensionality. The Apply functions are not meant to take. 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. 0 or above, to pick up the fix, enable project level setting "Data Engine Version" to 11. These are called pass-through functions because Microstrategy does not check the actual SQL construct and dumps it as is on the database. From the Select a Project drop-down list, select the project for which to assign the security role. CREATE and INSERT statements are not supported. Specify a name and location for the new security filter and click Save. Steps: 1. 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. Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Workaround 4: Create a metric based on the attribute Country, for example Max (Country). This document introduces how to apply conditional logic on a derived metric according to attribute form whose type is character. Return the sum of all Quantity fields in the OrderDetails table: SELECT SUM (Quantity) FROM OrderDetails; Try it Yourself ». g. This setting also applies to the use of security filters for creating an element cache. UnderstandingFunctionsinMicroStrategy 5 TheBasicsofMicroStrategyObjects,ObjectDefinitions,andFunctions 6 FunctionSyntaxandFormulaComponents 9Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. 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. The new VLDB Property has the following 3 options: If option 2 or 3 are selected, Cartesian Join Governing replaces Cartesian Join Warning and Cartesian Join Warning no longer works and becomes obsolete. x where report SQL statement containing semi-colon (;) in the Report Pre Statement 5 VLDB properties will cause report to fail in MicroStrategy 10. 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. In the VLDB Properties window, expand the folder called 'Tables'KB14618: How do pre/post statements in the VLDB properties affect the SQL statement when executing reports in Microstrateg… Number of Views 3. Follow the steps below to change the property. That Stored Proced has an Input Parameter which I need to. Base Table Join for Template. pass as Prompt answer. In general, ApplySimple can be used to create the following objects: •. Without this option all reports would execute their SQL pass by pass in a sequential order over a single database connection. Using linear and seasonal regression for Revenue F. Now set the Global Optimization VLDB Property to Remove Duplicate and Unused Passes and execute the. The SQL Date Format VLDB property can have a different value to the one set at the Project Level for a particular datamart report. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Note: The above caveats apply only when the "Do not do downward outer join" setting without automatic ordering is used. However, the SQL used to execute the report can still be viewed and obtained. It does not apply to situations where index creation occurs before insertion of data. A given VLDB setting can support or. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. For more information regarding post statements defined at the report level, refer to the following Technical Note: KB14618:. Select the Members tab. For more information, see Simple vs. The default syntax can be modified by using 'Column Pattern' VLDB property. 3. To simplify the explanation, this function is used to apply non-standard SQL expressions that MicroStrategy does not support or does not support. Customizing a CREATE TABLE statement is only possible for a permanent table. Reuses redundant SQL. The property is named "document grids from multiple datasets" and defaults to enabled but can be set to disabled. CONTENTS 1. 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. To set these properties, open the report in the Report Editor or Report Viewer. 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). However, the SQL used to execute the report can still be viewed and obtained. If you are upgrading to MicroStrategy 10. This setting can substantially reduce the number of SQL passes generated by MicroStrategy. 0 and higher). Sum is a group-value function. The GROUP BY Clause in. 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…. Instead, they are intended to enhance the MicroStrategy product by taking advantage of what the RDBMS platforms can offer. Analyze the low performance query using DBA knowledge, add. SELECT SUM(DISTINCT salary) AS "Total Salary" FROM employees WHERE salary > 25000; If there were two salaries of. 1. VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine. Viewing and Changing VLDB Properties. Attribute level: Select the desired join behavior for this attribute. VLDB Function. For Series this parameter is unused and defaults to 0. 4. As you type, matching objects are displayed in a drop-down. Uncheck the 'Use default inherited value' check box, if it is checked, and set the option to 'Permanent Table,' as. MicroStrategy’s OLAP functions are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. Ans: MicroStrategy handles metadata by centralizing it within its Intelligence. Subqueries (or correlated subqueries) are used infrequently but significantly in the MicroStrategy SQL Generation Engine. It is a Microstrategy way of conducting database particular preferences while making the report SQL. x report for a specific attribute using an ApplySimple statement as one of its forms. x, the only options were to drop tables or do nothing. For more details on performing outer joins between metrics at different dimensionalities, refer to the following MicroStrategy Knowledge Base documents: Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. Number of Views 822. REGION_ID REGION_ID, max(a13. Action If the CASE expression has only one branch -- i. In general, a user specifies a list of conditions and corresponding return values. Case Functions. Loading. Database Instance. [M1]:. Example: Create a new custom subtotal object. 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'. The VLDB property's behavior will be demonstrated using the following attribute and report. This calculation can be aggregated from the Employee level to the Region level. The syntax for the If function is IF (Condition, TrueResult, FalseResult) where:Explanation. A list of security roles in the project source opens in the main Developer pane. expression is an expression of the exact numeric or approximate numeric data type category, except for the bit data type. It has two options: Disable Set Operator Optimization: SQL will be generated as in previous versions. Criteria= the condition. Enter the values to use as arguments. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. " All the metrics in the report have been specified with outer joins, so theoretically the engine should not generate GODWFLAG in cube SQL and all rows of the intermediate table are. This issue has been addressed starting in MicroStrategy 9. Expand the 'Administration' Icon, and select the Database Instance Manager. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Loading × Sorry to interruptIn the Functions pane, hover over the If or Case function and click Edit. x. This setting provides two options - 'Permanent table' or 'True temporary table'. You can apply transformations to simple metrics but not for compound metrics. 1) When I execute the STored Procedure by setting it in PreSQL. 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. This document introduces how to apply conditional logic on a derived metric according to attribute form whose type is character. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. There are two options for this property: CREATE and INSERT statements are supported. ApplyAgg – Uses aggregate functions such as Sum, Max, and so on. The Preserve All Lookup Table Elements VLDB property is used to show all attribute elements that exist in the lookup table, even though there is no corresponding fact in the result set. For example, your report contains Store and Sum (Sales), and it is possible that a store does not have any sales at all. 0. In the examples in this article, we will be using a 12 TB database, appropriately named VLDB01. The downward outer join pass. Sum . Note that the SUM() function ignores NULL values. This is a database instance level VLDB setting. Choose one of the following: •. This article notes a scenario where no aggregation occurs in the SQL generated by MicroStrategy. Non-aggregatable metrics are defined using the dimensionality section of the metric editor. 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. These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. Note the values that are returned by M02=Sum(Case): Add a second dataset to the dossier. Intermediate Table Type. The First option, 'CREATE and. In general, a user specifies a list of conditions and corresponding return values. To access the parameters for the function, in the metric. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. From creating basic objects to building complex reports and analyzing data, you have the ability to create custom. x as the SQL hint VLDB property doesn't generate the desired SQL. By default, the Sum function will be used. 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. In MicroStrategy SQL Generation Engine, non-aggregatable metrics are used for this kind of calculation. The Moving Sum function returns a cumulative total of values based on a specified window size. Need to find the sum of the bill amount for particular orders. This article covers the Constant Column Mode VLDB property and its options and function in MicroStrategy Using Apply functions is recommended only when corresponding functionality does not exist in MicroStrategy. ) will apply. In some cases, it could be appropriate to change this setting for DB2 LUW. As you see, the sum of values in the quantity column in the table product is 7. VLDB Data Type . The functionality of Apply functions is provided by wrapping the expression, as a string, inside a dedicated (Apply) function call. If parentheses are required in the database syntax, it is the user's responsibility to provide them, e. [CATEGORY_ID] AS CATEGORY_ID, sum(a11. . Yes, my report is running a huge SQL Any advise? Thanks. You can apply transformations to simple metrics but not for compound metrics. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 7. If no ordering is specified, the result of some window functions (e. The CaseV function takes a numeric value M1 as input and compares it to another numeric value V1. Mostly you should do nothing about it. This function is used to display the ranking of values in a list relative to the other values. They can also help you take more advantage of the data. Use Count (Attribute@ID) to calculate total element number (uses count distinct if necessary) For Tandem databases, the default is Use ODBC Cursor. The ApplyAgg function itself is a group-value function and accepts facts, attributes, and metrics as input. However, you want to show all the store. Syntax. For example, if a ranking window function is used, the rank is computed with respect to the specified order. Multiple passes are generated only when necessary to resolve all the metric definitions. Note: The "From Clause Order" VLDB property is intended to control syntax only, not join behavior. Alternately, there is a VLDB property, "Engine attribute role options," which will allow the MicroStrategy SQL Engine to attempt to determine automatically when attribute roles are present in the schema and generate SQL accordingly. Other databases, such as some versions of Teradata, have a mix of the join standards and therefore need their own setting. Attribute form. A list of security roles in the project source opens in the main Developer pane. What I ended up doing is run the query without the Sum () Function and then use the Totals feature that is available on forms in Datasheet view. However, users can optimize this SQL for large data warehouses by changing the Sub Query Type VLDB property. Aggregate functions and subqueries are not. In MicroStrategy Developer, choose File > New > Report. 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. Governor. Generally, when null checking is used in metrics, the null checking is performed as part of the initial metric calculation. This setting can reduce the number of SQL passes generated by MicroStrategy. VLDB Settings. The VLDB Properties Editor opens. 10 / 10. -1 (Use value from higher level) Limiting Report Rows, SQL Size, and SQL Time-Out: Governing. CAUSE: The attribute form used for the 'group by' clause of the SQL generated is not an ID form. Metric-specific VLDB properties in Microstrategy - Metric-specific VLDB properties in Microstrategy courses with reference manuals and examples pdf. Help your customers get more out of the app experience with an engaging AI assistant that provides automatic answers or outputs in real time. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. This sometimes produces SQL that is expensive to run on the database, particularly if multiple attribute lookup tables are combined using cross joins. #. This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Watch free 3-5 minutes tutorial videos, with subtitles available in 9 languages, to build product fluency! Start learning. 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. 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 displays the descriptive information of each default VLDB property setting in the VLDB settings report. For information about accessing these properties, see the page reference for each property in the table below. Case. A VLDB database. The 'Group By ID Attribute' VLDB property is not applied in a MicroStrategy Desktop 8. For example, if attribute Region is 'Central' then derived metric value should be 'Profit + Cost'. Return the sum of the values over the requested axis. " In MicroStrategy SQL Generation Engine 8. Within a project, a security filter may be specified for any user. tion. How to avoid: By default, MicroStrategy uses database connection caching. '. However, end users have to provide both custom SQL and function inputs every time they use these functions in creating MicroStrategy objects like metrics, filters and so on. Function. 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. Enable Set Operator Optimization (if supported by database and [Sub Query. In contrast with warehouse partitioning, a metadata partitioning solution does not require a Partition Mapping Table (PMT) stored in the warehouse. g. Max(MovingSum(Sum(x){~},2)){@}VLDB (Very Large DataBase) properties allow you to customize the SQL that MicroStrategy generates. It is possible to disable the warning by setting ansi_warnings off but this has other effects, e. In the Source area, select a database instance for the database to access using Freeform SQL. This query does not return all desired elements of category from the Data Warehouse. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. 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. Beginning with MicroStrategy 9. The database was created with files stored directly in Azure blob storage , using a Premium Storage. The properties are saved in different folders, as indicated in the previous list. SQL Global Optimization. The Table Creation Type property tells the SQL Engine whether to create a table implicitly or explicitly. The outer function calculates the average of the inner function at the report level. Modify the SQL Date Format property to match either the MEMBER_NAME or raw ID. Beginning with MicroStrategy 9. Enable users to interact with personalized chat for further product discovery. Right-click the Customer attribute and select New Attribute form. A comment that passes instructions to a database optimizer about choosing an execution plan for a given SQL statement. If M1 equals V1, then a specified value can be returned. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 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. The SQL COUNT() function is used to count the rows in a table, and can be used with ‘ALL’ and ‘DISTINCT’ arguments. With MicroStrategy, SQL optimization is performed, by default, across passes corresponding to different elements of a Custom group when possible. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. 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. In general, a user specifies a list of conditions and corresponding return values. Example include ApplySimple, ApplyComparison, etc. select a11. 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. Example. Return the sum of all Quantity fields in the OrderDetails table: SELECT SUM (Quantity) FROM OrderDetails; Try it Yourself ». select a11. Some databases, such as DB2, support both Join 89 and Join 92. Syntax. There are three options available: No interaction - static custom group; Apply report filter to custom groupThis article notes how to remove LTRIM functions from SQL generated against OracleCa se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. Group by alias. MicroStrategy SQL Generation Engine will not automatically add parentheses around the list. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. MicroStrategy’s OLAP functions are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. By default a report with the Category attribute and the Revenue metric would generate the SQL statement as shown below. In general, a user specifies a list of conditions and corresponding return values. No set operators will be used. This is a database instance level VLDB setting. , row number) is non-deterministic. [TOT_DOLLAR_SALES]) AS Revenue into [ZZEA00] from [YR_CATEGORY_SLS] a11 Generally, when null checking is used in metrics, the null checking is performed as part of the initial metric calculation. 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. Apply Functions provide the capability for MicroStrategy customers to leverage functions specific to RDBMS but not standard in MicroStrategy. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Instead, they are intended to enhance the MicroStrategy product by taking advantage of what the RDBMS platforms can offer. It is used to insert any single-value, database-specific functions and simple operators directly into SQL. For all other valid Intermediate Table Type VLDB settings, the SQL does not reflect the values set for these properties. Assuming that users have two database instances, one for the. This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. The default syntax can be modified by using 'Column Pattern' VLDB property. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. 11: enable the Feature Flag "Defect fixes that may impact Data, SQL, MDX, CSI" within the Web Preferences -> Project Defaults. If M1 does not equal any of the values in the list, then it returns a default value. 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. Report results should be the same for all values of this setting. On the Freeform Sources tab, select Create Freeform SQL report. The Apply functions are not meant to take. x. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Although transformations can be applied to any attribute hierarchy, the Time hierarchy is used most often. Attribute. 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. The name of the new result column (i. The ApplySimple function is a single-value function. AS CUST_FIRST_NAME, a11. Returns the sum of all numbers in a list of values. Using Apply functions is recommended only when corresponding functionality does not exist in MicroStrategy. For details on each of these. 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). x attempts to combine metric calculations and attribute lookups into one pass of SQL. A solution is provided. This setting is used as an optimization for some databases which perform better when columns coming from. Open the VLDB Properties Editor this way. Double-click the CUST_LAST_NAME column to add it to the Form expression pane on the right. •. x. The attribute uses a CASE statement to replace NULL values with -999. There are two options for this property: CREATE and INSERT statements are supported. Case can be used for categorizing data based on multiple conditions. For details on each of these. 1 client subtotal behavior. (For step by step instructions on creating a new plug-in, please navigate to Home > Web SDK > Customizing MicroStrategy Web > Web Customization Editor. Example. You can click an object or continue to type. The following list of articles can be used for further reference regarding the 'derived table' behavior with MicroStrategy SQL engine. Two different passes of SQL for metrics which only differ via a simple filter are note merged via SQL Global Optimization levels 3 and 4 despite notes that it can. This type of formula is called a base formula, which can contain arithmetic operators, attributes, facts, group functions, and non-group functions. This article explains the behavior of the commit level VLDB property35. FROM OrderDetails WHERE ProdictId = 11; Try it Yourself » Use an Alias Give the summarized column a name by using the AS keyword. x and 10. The Engine generates multi-pass SQL against the ORDER_FACT table and first retrieves the SUM (ORDER_AMT) at the level. As you type, matching objects are displayed in a drop-down. MicroStrategy pushes the calculations for the following list of built-in OLAP functions down to SAP HANA using the associated SQL patterns. This can be inconvenient when reports do not hit Intelligent Cubes, because the report designer will need to have access to the log file on the Intelligence Server machine. Metric with an IF Function. 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. Sum . In general, a user specifies a list of conditions and corresponding return values. There is no VLDB setting associated with this option. Generate Oracle AWR report or monitor the database to identify the low performance query. REGION_NAME) REGION_NAME,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. Example: The SQL below is from a report that can use parallel execution. The Use default inherited value option indicates the level that is active, while the SQL preview box. Multipass SQL statements in Freeform SQL are not supported in Microstrategy. For more information on the SUM() function, you can read this complete explanation of the SQL SUM() function. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 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. MicroStrategy value prompts do not allow multiple values. x includes a VLDB property, 'CREATE and INSERT Support,' under the Tables folder, at the database instance level. The chart below shows the order of precedence of the VLDB properties: The arrows depict the override authority of. Intelligence Server computes the new fact Trunc([Dollar Sales]) first and then uses the Sum function to sum the new fact for each region. 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. Join common key on both sides. In these cases, the MicroStrategy SQL Engine uses the value set in the VLDB setting, 'Fallback Table Type'. 0. This metric divides the sum of VOL fact at report level by [Net Weight] after applying it a character replace at BBDD level with ORACLE's replace function (it seems that the BBDD is ORACLE), and breaks it down by product. Example: The SQL below is from a report that can use parallel execution. 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. Splitting the fraction: Numerator: Sum (VOL) {~} Denominator: Max ( ApplySimple ("replace (#0, ',', '. This article describes how to show distinct total value via setting distinct subtotal with across level in Microstrategy Developer. the aggregation function is not applied to the fact for the metric calculation. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 7. Please note that the changes to this object will not be visible until the cube. x and 10. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. This article explains how the applycomparison function works in MicroStrategy[IM001:0: on SQLHANDLE] [Microsoft][ODBC Driver Manager] Driver does not support this function. If you are editing the Case function, use the values in step 8. For complete details about all VLDB properties, see SQL Generation and Data Processing: 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. For more information on the SUM() function, you can read this complete explanation of the SQL SUM() function. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. This is an OLAP function. Returns the sum of all numbers in a list of values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. When you need to use an Apply function, MicroStrategy. Select the Security Filters tab. It controls whether the indexes will be created separately for each column or whether the indexes will be created together for multiple columns. It is possible to disable the warning by setting ansi_warnings off but this has other effects, e. Column aliases allow you to specify a more appropriate data type that can help avoid errors in your SQL. Select the Members tab. For more details on this latter scenario, consult the following MicroStrategy Knowledge Base. 2) Create Metric2 as the RunningSum of Metric1. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. In MicroStrategy, a hint can be defined in VLDB properties to appear within a MicroStrategy-issued SQL statement. When MicroStrategy queries the data warehouse, the software determines which condition evaluates as true and then returns the value that the. 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.