In MicroStrategy Developer, choose File > New > Report. Group by position. The property may be set project wide in the database instance, or on a report-by-report basis. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. x as the SQL hint VLDB property doesn't generate the desired SQL. x and 10. MicroStrategy value prompts do not allow multiple values. 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. x includes a VLDB property, 'CREATE and INSERT Support,' under the Tables folder, at the database instance level. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. The name of the new result column (i. After a report is run, we keep the connection open (DB connection timeout values apply). In general, a user specifies a list of conditions and corresponding return values. 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. The following list summarizes the metric-specific VLDB properties that can be set at the metric level. pandas. 37. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. The downward outer join pass. 1, VLDB properties may be enabled in Intelligent Cube reports and user reports to include Dynamic Sourcing diagnostic messages in SQL View. Select one: To create a new security filter, click New. This is equivalent to the method numpy. Intelligence Server computes the new fact Trunc([Dollar Sales]) first and then uses the Sum function to sum the new fact for each region. Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. What is a subquery? A subquery is a secondary SELECT. To do so, click Tools > Report Details Page after the report has been executed, as shown below: This will bring up the Report Details window for the specific report. REGION_ID REGION_ID, max(a13. The SQL can be obtained from the SQL Statement section, as shown below: Published: Apr 13, 2017. Users will experience an issue when modifying database instance-level VLDB properties where any changes made to the VLDB properties such as Column Pattern. The image below shows the SQL view of the Report Pre Statement 5s output. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. From creating basic objects to building complex reports and analyzing data, you have the ability to create custom. 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. If you are upgrading to MicroStrategy 10. 1) Create Metric 1 which is the sum of the fact that is to be in the columns. These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. -1 (Use value from higher level) Limiting Report Rows, SQL Size, and SQL Time-Out: Governing. In MicroStrategy, a hint can be defined in VLDB properties to appear within a MicroStrategy-issued SQL statement. For information about accessing these properties, see the page reference for each property in the table below. Returns the date of the first day of the month in which date or timestamp occurs. x mixed case columns names for a DB2 database by default have SQL generated with quote characters enclosing the name . Case can be used for categorizing data based on multiple conditions. Examples of SQL SUM() Given below are the examples of SQL SUM(): Example #1 – Using a single column. 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. IMPORTANT: If Report Pre and Post Statements are defined in report or template level VLDB Properties, these will override the settings in database instances. To use previously defined in Db2 function in MicroStrategy, you can use the MicroStrategy built-in Apply (Pass-Through) Functions or use Freeform SQL. A given VLDB setting can support or. This flexibility is an important benefit of VLDB properties because it permits adjustment of many levels such as: REPORT - highest priority. AS CUSTOMER_ID, from a11. The SUM () function returns the total sum of a numeric column. a temp table is created but not referenced in a later pass. For Compound Profit to be dynamically aggregated correctly, you change the dynamic aggregation function to Sum. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. x. 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. x. 4. Pass 1. Select the Security Filters tab. However, the SQL used to execute the report can still be viewed and obtained. [M1]:. In such a case, Report Pre and Post Statements from all database instances will be ignored. As these accounts do not have access to "Configuration Managers" in the Administration tab, the only way to view the VLDB. 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. Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. Group by column. See full list on When calculating the grand total over yearly revenue, the Analytical Engine simply sums the three distinct values and produces the right total, without the inflation that would occur if the sum were taken over the 12 rows displayed in the report. 1. g. e ('Call [SP]') it does not. e. 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. OR, to convert an existing filter into a security filter, click Import. In these cases, the MicroStrategy SQL Engine uses the value set in the VLDB setting, 'Fallback Table Type'. For example, the SQL SELECT statement below returns the combined total salary of unique salary values where the salary is above $25,000 / year. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. 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. The ApplyAgg function is used to define simple metrics or facts by using database-specific, group-value functions. Note that the or-dering only affects window function processing but not necessarily the final order of the result. Tutorial project is used here. Subqueries (or correlated subqueries) are used infrequently but significantly in the MicroStrategy SQL Generation Engine. This VLDB property specifies the type of intermediate storage structures the SQL Engine creates. This allows you to use MicroStrategy's built-in functions in your qualification. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. sum #. 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. This version of the product is no longer supported in accordance with MicroStrategy's support lifecycle. By default a report with the Category attribute and the Revenue metric would generate the SQL statement as shown below. 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. (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. Viewing and Changing VLDB Properties. Some databases, such as DB2, support both Join 89 and Join 92. The current year can be returned by putting: Year (CurrentDate ()) for your comparison. Aggregate functions and subqueries are not. Open MicroStrategy Developer. 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 SQL Generation Engine 8. 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. Syntax. MicroStrategy SQL Generation engine 10. x. 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. It is, consequently, displaying a total which is. 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. A list of security roles in the project source opens in the main Developer pane. This is a database instance level VLDB setting. 11: enable the Feature Flag "Defect fixes that may impact Data, SQL, MDX, CSI" within the Web Preferences -> Project Defaults. Some databases, such as Oracle, do not support the ANSI 92 standard yet. 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. In the VLDB Properties window, expand the folder called 'Tables'Normally, MicroStrategy SQL Generation Engine 9. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Here’s the result: sum_quantity. Sum . This is a single-value function. Several additional VLDB properties are introduced with MicroStrategy 9. Group by alias. The SQL SUM () Function. =SUMIF (range, criteria, [sum_range]) Range = range of cells where you want to check the criteria. 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. Visit the MicroStrategy download site to download the latest supported version of this product. compound metrics. To simplify the explanation, this function is used to apply non-standard SQL expressions that MicroStrategy does not support or does not support. SYMPTOM. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. This setting provides two options - 'Permanent table' or 'True temporary table'. No pre-query is required and MicroStrategy can produce derived table or common table expression syntax. In the Report Editor click on 'Data'> 'VLDB Properties' option, as illustrated below. The formula of a simple metric is based on group functions (such as sum or average). For example, a transformation metric can help a user compare last month's revenue to this month's revenue. In contrast with warehouse partitioning, a metadata partitioning solution does not require a Partition Mapping Table (PMT) stored in the warehouse. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. The resulting SQL will contain just the Metric Alias. The Moving Sum function returns a cumulative total of values based on a specified window size. Sum <Distinct, FactID, UseLookupForAttributes>(Argument)Where: Argument is an attribute, fact, or metric representing a list of numbers. However, the expression '' alone will not check for NULLs although the Very Large Database (VLDB) setting is activated. The following VLDB properties can be used in conjunction to force the final pass of the report to apply the report filter; Additional Final Pass Option and Apply. The Engine generates multi-pass SQL against the ORDER_FACT table and first retrieves the SUM (ORDER_AMT) at the level. TEMPLATE. 4. They act as containers for non-standard SQL expressions that MicroStrategy does not support. The Profit metric is a simple sum of the Profit fact. Base Table Join for Template. ) User-defined. I want to see the companies which deliver the most sold items in my DB. Key distinctions of the RANK function are that it requires an order by clause and does not support a window clause. 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. This article notes a scenario where no aggregation occurs in the SQL generated by MicroStrategy. As seen below, the total subtotal function and dynamic aggregation function for MetricTest was changed from Sum to Maximum. Syntax. 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. How to change the syntax is described in detail by using examples. Determines how distinct counts of values are retrieved from partitioned tables. The MicroStrategy SQL Engine will join database tables together based on the lowest level attributes that MicroStrategy Architect assigns to each table. For more information, see Simple vs. For example, the before and after SQL that is generated for a. Intermediate Table Type. A list of security roles in the project source opens in the main Developer pane. ADDITIONAL INFORMATION:. Rank) calculated in Analytical Engine" found under the 'Metrics' folder in the list of VLDB properties. 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. 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. In the MicroStrategy Tutorial, a report with the Subcategory attribute and the Freight and Discount metrics generates the following SQL (using Microsoft SQL Server): select. MicroStrategy SQL Generation Engine 9. Browse to the filter you want to convert. This is a known issue prior to MicroStrategy SQL Engine 9. Create the statistics database instance. This article explains the behavior of the commit level VLDB property35. The first is to enable the SQL Hint VLDB property and include a TOP (or BOTTOM) clause. This article describes how to create a metric with an attribute as a filter using a Case statement in a Visual Insight dashboard in MicroStrategy Web. This article describes how to show distinct total value via setting distinct subtotal with across level in Microstrategy Developer. The maximum number of rows returned to the Server for the final result set. A VLDB database. Case. Let us create one simple table named numbers and store the. 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. This article describes how to use wildcards to display temporary table names in pre/post statements. The properties are saved in different folders, as indicated in the previous list. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. Where a report can use more than one database instance, an intermediate table may be created in only one database, and the VLDB Properties for that SQL. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. The database was created on a SQL Server VM in Azure by loading data from text files in Azure Blob Storage, using PolyBase . This displays the descriptive information of each default VLDB property setting in the VLDB settings report. 0. If you are upgrading to MicroStrategy 11. The VLDB Properties Editor opens. Returns the sum of all numbers in a list of values. x. Option 1: Keep the backward compatibility with MicroStrategy 2019 where SQL queries are governed by Cartesian Join Warning VLDB. Go to Tools menu to enable the option “Show advanced settings” if it is not. Ans: MicroStrategy enables ad hoc analysis through an intuitive interface. the alias) is sum_quantity. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. Nested aggregation can also be performed using aggregation functions applied to metrics. To set these properties, open the report in the Report Editor or Report Viewer. 1, VLDB properties may be enabled in Intelligent Cube reports and user reports to include Dynamic Sourcing diagnostic messages in SQL View. 7. The CaseV function takes a numeric value M1 as input and compares it to another numeric value V1. If you want more than one sum in the result, use GROUP BY to create groups, and then select a sum (somecolumn). REGION_ID REGION_ID, max(a13. Watch free 3-5 minutes tutorial videos, with subtitles available in 9 languages, to build product fluency! Start learning. Use Count (Attribute@ID) to calculate total element number (uses count distinct if necessary) For Tandem databases, the default is Use ODBC Cursor. Action If the CASE expression has only one branch -- i. x and 10. MSTR Transformation Metric with no aggreagation; MSTR Defining sets of privileges: Security roles; MSTR VLDB SQL optimization tipsThe Apply functions also hand off to your RDBMS functions that are specific to your database. 5. If it is necessary to apply different connection parameters to different warehouses using Pre Statement VLDB Properties, it is possible to use the Table Pre Statement VLDB Properties instead. Group by position. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. Passes that hit the same fact table across different elements of a custom group are merged provided that they satisfy certain conditions. 1) When I execute the STored Procedure by setting it in PreSQL. [CATEGORY_ID] AS CATEGORY_ID, sum(a11. This procedure assumes you are already working with a metric in the Metric Editor. Navigate to Tools > Advanced Settings > VLDB Properties to open the VLDB properties editor. Helps optimize custom group banding when using the Count Banding method. The 1NF table will have one number per row, and will contain more rows than the initial table. 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. The above example would not be valid with multiple months in the answer because the >= expects single values for its operands. 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 window size is a parameter which tells the function how many of the values should be included in the calculation. The chart below shows the order of precedence of the VLDB properties: The arrows depict the override authority of. When using this setting, dimensionality order overrides template order. Although tables and indexes are the most important and commonly used schema objects, the database supports many other types of schema objects, the most. Hi, I am having the same problem with Microstrategy Version 8. 3. x attempts to combine metric calculations and attribute lookups into one pass of SQL. From the Select a Project drop-down list, select the project for which to assign the security role. 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. Since the report or template is not associated with a specific database instance, the primary. They act as containers for non-standard SQL expressions that MicroStrategy does not support. KB17514: Using the 'Preserve all final pass result elements' VLDB property at attribute level in MicroStrategy SQL Generat… Number of Views 6. 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). Double-click the security role you want to assign to the user or group. Launch Project Configuration, select "SQL Data warehouses" under "Database instances" tab. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. x database and leads to different SQL. The ApplyAgg function itself is a group-value function and accepts facts, attributes, and metrics as input. 9 / 10. Case() and CaseV() functions are Analytical Engine functions, i. After a report is run, we keep the connection open (DB connection timeout values apply). If parentheses are required in the database syntax, it is the user's responsibility to provide them, e. a temp table is created but not referenced in a later pass. Note how adding an unrelated dataset unexpectedly changes the data returned by M02=Sum(Case): Cause This is a known issue in MicroStrategy 2019. Specifies that SUM returns the sum of unique values. 5. 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. For use cases, examples, sample code, and other information on every VLDB property. 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. Double-click the CUST_LAST_NAME column to add it to the Form expression pane on the right. This setting can reduce the number of SQL passes generated by MicroStrategy. CAUSE: The MicroStrategy SQL Generation Engine distinguishes between the SQL passes generated for the Report (to return the data for the result set) and the passes generated for the datamart (to create and populate the datamart table) when applying the VLDB settings. Grouping. g. 82K KB11125: How to control the join order of metrics in the final pass when using the "Do. 7. The Security Filter Editor opens. This knowledge base article describes an issue in MicroStrategy 10. In the VLDB Properties, locate option "Distinct/Group by Option (when no aggregation and not table key)" under Select/Insert tab. If you choose Temp Table Join. Note: This behavior does not apply to server-level partitioning, in which tables are partitioned natively within the database. You can use them in many different capacities, which include, creating or modifying both schema and user objects. AS CUSTOMER_ID, a11. To see an example that uses this technique, see Estimating dynamic aggregation values with different aggregation functions. In general, a user specifies a list of conditions and corresponding return values. Right-click the Customer attribute and select New Attribute form. 0, a VLDB property is available to control. Notice that the Yearly Revenue subtotal is the sum of all four rows in the grid: Now change the VLDB properties to the following: Under Subtotal and Aggregate Compatibility, select '7. Attribute form. 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. If not, the permanent table’s option is the default setting. Open the VLDB Properties Editor to display the VLDB properties for the level at which you want to work. The Use default inherited value option indicates the level that is active, while the SQL preview box. 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. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. MicroStrategy’s OLAP functions are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. By default, the Sum function will be used. MicroStrategy SQL Generation Engine will not automatically add parentheses around the list. By default, the metrics Compound Profit and Profit Margin do not use a dynamic aggregation function. 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. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. 7. 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. What function does the MicroStrategy Intelligence Server serve? Ans: Query processing; Metadata repository management; Data caching and Intelligent Cubes; Security and authentication; Load balancing; 47. All articles. Report results should be the same for all values of this setting. The post-execution SQL that was available in Narrowcast can be replaced by implementing post-report SQL VLDB properties. These settings can be changed in the VLDB Properties dialog box for either reports or the database instance. Select Data/VLDB Properties. In MicroStrategy SQL Generation Engine, non-aggregatable metrics are used for this kind of calculation. Generate report SQL (see the table below under ‘Without Setting’). The property is named "document grids from multiple datasets" and defaults to enabled but can be set to disabled. Please note that the changes to this object will not be visible until the cube. They act as containers for non-standard SQL expressions that MicroStrategy does not support. CREATE and INSERT statements are not supported. In the Source area, select a database instance for the database to access using Freeform SQL. The Profit metric is a simple sum of the Profit fact. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. Most of MicroStrategy’s OLAP functions (24 out of 31) are calculated via SQL in Teradata rather than in the MicroStrategy analytical engine. VLDB Insert. CAUSE: MicroStrategy can support multiple (more than 5) pre-statements to put in a report. Enable Set Operator Optimization (if supported by database and [Sub Query Type]): Use set operators when possible. There are two options for this property: CREATE and INSERT statements are supported. The property is shown in the below screenshot. Select the Security Filters tab. This article describes how to change the syntax for column names using the column pattern VLDB propertyIn SQL, the formula commonly becomes part of the SELECT clause of the SQL command. You can click an object or continue to type. Some databases do not support implicit creation, so this is a database-specific setting. g. Use Count (Attribute@ID) to calculate total element number (uses count distinct if necessary) For Tandem databases, the default is Use ODBC Cursor. Mostly you should do nothing about it. Instead, they are intended to enhance the MicroStrategy product by taking advantage of what the RDBMS platforms can offer. You can apply transformations to simple metrics but not for compound metrics. 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. For DataFrames, specifying axis=None will apply the aggregation across both axes. To access the parameters for the function, in the metric. CONTENTS 1. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. (For step by step instructions on creating a new plug-in, please navigate to Home > Web SDK > Customizing MicroStrategy Web > Web Customization Editor. VLDB Function. SQL Global Optimization. This property is found in the Select/Insert folder of the VLDB property editor: This property has four options: Group by expression. The SQL can be obtained from the SQL Statement section, as shown below: Published: Apr 13, 2017. xml file in the "Program Files (x86)Common FilesMicroStrategy" folder on a machine with MicroStrategy Developer installed and create a backup of this file, and then edit it. The possible values for this VLDB property are: • Permanent table46. In some cases, it could be appropriate to change this setting for DB2 LUW. SQL Global Optimization. Click here to view help for the latest version of this product or search MicroStrategy Community. UnderstandingFunctionsinMicroStrategy 5 TheBasicsofMicroStrategyObjects,ObjectDefinitions,andFunctions 6 FunctionSyntaxandFormulaComponents 9 Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. x and 10. x, the only options were to drop tables or do nothing. Create a new plug-in and give it a meaningful name. To do this, the "Preserve all final pass result elements" VLDB property must be set at both attribute and report level. To provide a reasonable level of generality, the feature is based on a 'pattern and arguments' scheme. The option is available in the Project Level VLDB properties under "Query Optimizations" as seen below. The VLDB property's behavior will be demonstrated using the following attribute and report. The user should locate the VLDB. •. Aggregate functions and subqueries are not. In the condition you can use logical operator (<,>,<>,=) and wildcards (*,$) for partial conditions. 5, multi-source reports inherit the Report Pre/Post Statement VLDB setting only from…Normally, MicroStrategy SQL Generation Engine 9. This allows queries to run faster since there are no CREATE TABLE or DROP TABLE statements to catalog, no corresponding locks on the created tables or the system. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. The window size is a parameter which tells the function how many of the values should be included in the calculation. ; Distinct is a TRUE/FALSE parameter that allows you to. By design, however, MicroStrategy SQL Generation Engine 8. •. . Open the VLDB Properties Editor this way. 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 ApplyAgg function is used to define simple metrics or facts by using database-specific, group-value functions. If the report uses only inner joins, then the only thing that changes is the table order. 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. tion. g. The database was created with files stored directly in Azure blob storage , using a Premium Storage. Users can explore, filter, and visualize data with drag-and-drop functionality. 4. Browse to the filter you want to convert and click Open. CAUSE: By checking the SQL statements of the report, there is no "sum" or "group by" statement.