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. The MicroStrategy SQL Engine will join database tables together based on the lowest level attributes that MicroStrategy Architect assigns to each table. 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. The SQL SUM () Function. We will calculate the total value of SQL numbers using the SUM() function. 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. 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. The Security Filter Editor opens. The New Grid dialog box opens. Note the values that are returned by M02=Sum(Case): Add a second dataset to the dossier. This article describes how the "Set Operator Optimization" VLDB property works in MicroStrategy Controls whether tables are joined only on the common keys or on all common columns for each table. Some databases, such as DB2, support both Join 89 and Join 92. The database was created with files stored directly in Azure blob storage , using a Premium Storage. 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. 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. In general, a user specifies a list of conditions and corresponding return values. This allows the FOJ to be rewritten to a different kind of join in the query. To access the parameters for the function, in the metric. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. You can change VLDB properties to alter the syntax of a SQL statement and take advantage of database-specific optimizations. ) From the Tools menu, select Show Advanced Settings. x report for a specific attribute using an ApplySimple statement as one of its forms. Grouping. (0 = unlimited number of rows; -1 = use value from higher level. The location of each property in the CREATE TABLE statement is given below. In MicroStrategy, a hint can be defined in VLDB properties to appear within a MicroStrategy-issued SQL statement. Example Name the column. Customizing a CREATE TABLE statement is only possible for a permanent table. The maximum number of rows returned to the Server for the final result set. g. Function. 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. Specify a name and location for the new security filter and click Save. The 'Where clause driving table' Very Large Database (VLDB) property indicates to the MicroStrategy Engine which table to use when a filter needs to be applied. 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. the alias) is sum_quantity. For Compound Profit to be dynamically aggregated correctly, you change the dynamic aggregation function to Sum. This article covers the purpose of the where clause driving table property. For information on connecting to databases, see Connect to Databases. Modifying any VLDB property should be performed with caution only after understanding the effects of the VLDB settings that you want to apply. 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. The First option, 'CREATE and. Create a metric with the ApplySimple statement below as its definition and name it. Define the statistics and enterprise warehouse database. In general, a user specifies a list of conditions and corresponding return values. Expand the 'Administration' Icon, and select the Database Instance Manager. A VLDB database. The following three options are available for the VLDB property. Using linear and seasonal regression for Revenue F. MicroStrategy pushes the calculations for the following list of built-in OLAP functions down to SAP HANA using the associated SQL patterns. 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. x. Double-click the security role you want to assign to the user or group. 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. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. This is a database instance level VLDB setting. The following settings are advanced properties which are. 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. 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. Passes that hit the same fact table across different elements of a custom group are merged provided that they satisfy certain conditions. By default usually MicroStrategy treats all column names as upper case only, however in DB2 (and potentially other databases) mixed case columns are possible in a case sensitive database collation. The Apply functions are not meant to take the place of the standard MicroStrategy functions. ')"; [Net Weight. Group by position. 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). Go to Tools menu to enable the option “Show advanced settings” if it is not. The image below shows the SQL view of the Report Pre Statement 5s output. 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. All of the template attributes will be considered as a unit. This document introduces how to apply conditional logic on a derived metric according to attribute form whose type is character. However, users can optimize this SQL for large data warehouses by changing the Sub Query Type VLDB property. However, the SQL used to execute the report can still be viewed and obtained. This VLDB settings influence the table creation type in the SQL passed to the Teradata database when Intermediate Table Type is set to True Temporary. Visit the MicroStrategy download site to download the latest supported version of this product. Sum . MicroStrategy may not be able to provide additional code on this matter even though. Select the Database Instance used for the project warehouse, right-click and select 'VLDB properties'. x and later). The following list of articles can be used for further reference regarding the 'derived table' behavior with MicroStrategy SQL engine. The default syntax can be modified by using 'Column Pattern' VLDB property. 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. Set up the Enterprise Manager. x where report SQL statement containing semi-colon (;) in the Report Pre Statement 5 VLDB properties will cause report to fail in MicroStrategy 10. By default a report with the Category attribute and the Revenue metric would generate the SQL statement as shown below. Define the statistics and enterprise warehouse database. There are two options for this property: CREATE and INSERT statements are supported. This type of formula is called a base formula, which can contain arithmetic operators, attributes, facts, group functions, and non-group functions. In such a case, Report Pre and Post Statements from all database instances will be ignored. x database and leads to different SQL. Select the Members tab. For example, a transformation metric can help a user compare last month's revenue to this month's revenue. The Security Filter Editor opens. 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. A given VLDB setting can support or. This article does contain a solution. Modify the VLDB property you want to change. This calculation can be aggregated from the Employee level to the Region level. After running a report containing the attribute "Subcategory" and metric "Sum of COST", "Sum of COST" is found not aggregated but just listed all the related records in the data source file. The SUM () function returns the total sum of a numeric column. That is, we can define the order in which operations are performed, optimization level, joins intermediate steps, Hints, and many more things that even go into advanced complexity. 2 metric aggregations will not be dimensionality aware. This document discusses Microsoft SQL Server Database support in MicroStrategy, provides an overview of the integration, summarizes supported workflows, and describes configuration and implementation details. The Profit metric is a simple sum of the Profit fact. In the Database Instance Manager, right-click the database instance you want to modify VLDB settings for, and choose VLDB Properties. This preference is located under the Tools menu > My Preferences > Editors tab > Filter Options, in which the first option, "Show advanced qualification," should be checked. Examples of SQL SUM() Given below are the examples of SQL SUM(): Example #1 – Using a single column. =SUMIF (range, criteria, [sum_range]) Range = range of cells where you want to check the criteria. 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. Function. 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. Expand the 'Administration' Icon, and select the Database Instance Manager. This issue has been addressed starting in MicroStrategy 9. From creating basic objects to building complex reports and analyzing data, you have the ability to create custom. For information on connecting to databases, see Connect to Databases. For example, the SQL SELECT statement below returns the combined total salary of unique salary values where the salary is above $25,000 / year. Choose one of the following: •. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. In MicroStrategy Developer, log into the Server Project Source as a user with administrative privileges. The calculation can restart based on attributes identified in the parameter settings. The Moving Sum function returns a cumulative total of values based on a specified window size. 8 and up . Embedded Analytics Solutions Solutions; Financial Services; Healthcare; Retail; GovernmentThis article explains the behavior of the commit level VLDB propertyTo simplify the explanation, this function is used to apply non-standard SQL expressions that MicroStrategy does not support or does not support. They act as containers for non-standard SQL expressions that MicroStrategy does not support. 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. Browse to the filter you want to convert and click Open. g. The functionality of Apply functions is provided by wrapping the expression, as a string, inside a dedicated (Apply) function call. Tell the usage of command manager? The command manager is used to save the text commands which can be executed as scripts. This setting is used as an optimization for some databases which perform better when columns coming from. the aggregation function is not applied to the fact for the metric calculation. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. Non-aggregatable metrics are defined using the dimensionality section of the metric editor. 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. In the examples in this article, we will be using a 12 TB database, appropriately named VLDB01. For complete details about all VLDB properties, see SQL Generation and Data Processing: VLDB Properties. , row number) is non-deterministic. 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. SQL Global Optimization. x introduces a third option to the VLDB Property "Drop Temp Table Method. 5, multi-source reports inherit the Report Pre/Post Statement VLDB setting only from…Normally, MicroStrategy SQL Generation Engine 9. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. a temp table is created but not referenced in a later pass. g. The ApplySimple function is a single-value function. This occurs when the data type of the. The metric join type, described in the previous section, is not the only VLDB property that affects metrics. Below is the supported OLAP functions by MicroStrategy with associated SQL pattern. the MicroStrategy SQL Generation Engine generates the following SQL for a report in Tutorial that requests the sum of units received for each Item, Quarter and. Axis for the function to be applied on. This article explains the behavior of the commit level VLDB property35. Insert a Percent to Total metric on Profit at the Quarter level: Add a Set Qualification on Revenue in the Report Filter to show only the top 100: Change the following VLDB settings. Yes, my report is running a huge SQL Any advise? Thanks. 1. CREATE and INSERT statements are not supported. Tutorial project is used here. Mostly you should do nothing about it. Example include ApplySimple, ApplyComparison, etc. This setting can substantially reduce the number of SQL passes generated by MicroStrategy. 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. To simplify the explanation, this function is used to apply non-standard SQL expressions that MicroStrategy does not support or does not support. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. Since the report or template is not associated with a specific database instance, the primary. You can use the SQL DISTINCT clause within the SQL SUM function. When a Freeform SQL report's query is submitted to the database, the entire query text is sent using a single ODBC SQLExecDirect call. You can copy the content in the report using the Ctrl+C keys on your keyboard, then paste the information into a text editor or word processing program. 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. Set up the Enterprise Manager. g. . In general, a user specifies a list of conditions and corresponding return values. 9 / 10. The ApplyAgg function itself is a group-value function and accepts facts, attributes, and metrics as input. Multipass SQL statements in Freeform SQL are not supported in Microstrategy. e. On the Freeform Sources tab, select Create Freeform SQL report. Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. Let us create one simple table named numbers and store the. This article notes a scenario where no aggregation occurs in the SQL generated by MicroStrategy. This is a single-value function. MONTH_ID IN (#E1). As you type, matching objects are displayed in a drop-down. Rank) calculated in Analytical Engine" found under the 'Metrics' folder in the list of VLDB properties. The last statement can contain multiple SQL statements concatenated by “;”. MicroStrategy value prompts do not allow multiple values. Return the sum of all Quantity fields in the OrderDetails table: SELECT SUM (Quantity) FROM OrderDetails; Try it Yourself ». Database instance, report, and templateSYMPTOM: The user has a report where the VLDB property of SQL Global Optimization has been set as "Level 4: Level 2 + Merge All Passes with Different WHERE. MicroStrategy SQL Generation engine 10. The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. Click here to view help for the latest version of this product or search MicroStrategy Community. pandas. Assuming that users have two database instances, one for the. , one condition, a true expression and a false expression -- the MicroStrategy IF function may be used instead. That Stored Proced has an Input Parameter which I need to. Metric-specific VLDB properties in Microstrategy - Metric-specific VLDB properties in Microstrategy courses with reference manuals and examples pdf. on how division by zero is handled and can cause failures when your queries use features like indexed views, computed columns or XML methods. If the option for multiple passes is selected, all metric calculations will be performed in separate passes. To use previously defined in Db2 function in MicroStrategy, you can use the MicroStrategy built-in Apply (Pass-Through) Functions or use Freeform SQL. DATABASE INSTANCE. The above example would not be valid with multiple months in the answer because the >= expects single values for its operands. The display format for dates does not change even after changing the SQL Date format and Date Pattern settings under VLDB properties of the project in MicroStrategy Developer. Criteria= the condition. For Series this parameter is unused and defaults to 0. Steps: 1. The ApplyAggregate, or ApplyAgg() function, can be used to bypass the SQL parser with mathematical functions. 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, right-click a metric and select Edit. The hierarchy, or order of precedence, for VLDB properties is outlined in the. Example: Create a new custom subtotal object. Multiple passes are generated only when necessary to resolve all the metric definitions. 4. ; In some limited cases you can rewrite the aggregate to avoid. This section focuses on the VLDB properties that are set at the metric and report level. The database was created on a SQL Server VM in Azure by loading data from text files in Azure Blob Storage, using PolyBase . Expand the folder to see what VLDB. Is a constant, column, or function, and any combination of arithmetic, bitwise, and string operators. SELECT SUM(DISTINCT salary) AS "Total Salary" FROM employees WHERE salary > 25000; If there were two salaries of. FROM OrderDetails WHERE ProdictId = 11; Try it Yourself » Use an Alias Give the summarized column a name by using the AS keyword. This article explains how the applycomparison function works in MicroStrategy[IM001:0: on SQLHANDLE] [Microsoft][ODBC Driver Manager] Driver does not support this function. CONTENTS 1. The Create New Form Expression dialog box opens. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. e. This article describes the purpose of the Sub Query Type VLDB property in MicroStrategy. Depending on your MicroStrategy product and licensing, this function may not be available. . Since the report or template is not associated with a specific database instance, the primary. The example below outlines how to create a Sum custom subtotal that only totals the last two metric values . The current year can be returned by putting: Year (CurrentDate ()) for your comparison. The GROUP BY Clause in. Rank. Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. This displays the descriptive information of each default VLDB property setting in the VLDB settings report. We have focused on the features that have been developed specifically to support and enhance the SQL Server integration. The functions that can be used are the movingdifference or movingsum functions. Create a new Report: Add Quarter, Customer, and Profit to the template. tion. x. For raw ID, in the above example, SQL Date Format. To provide a reasonable level of generality, the feature is based on a 'pattern and arguments' scheme. It is, consequently, displaying a total which is. Viewing and Changing VLDB Properties. This query does not return all desired elements of category from the Data Warehouse. REGION_ID REGION_ID, max(a13. It is a Microstrategy way of conducting database particular preferences while making the report SQL. ACTION: This is addressed MicroStrategy 11. With VLDB properties correctly configured, a report can join to some lookup tables using outer join and others using inner join. 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. A comment that passes instructions to a database optimizer about choosing an execution plan for a given SQL statement. e. Metric with an IF Function. g. 3. The SQL COUNT() function is used to count the rows in a table, and can be used with ‘ALL’ and ‘DISTINCT’ arguments. Transformations allow you to apply an attribute-element based offset to compare metric data. Workaround 4: Create a metric based on the attribute Country, for example Max (Country). This property exists at the Database instance, Report and Metric levels:MicroStrategy SQL Generation Engine makes it easy to show data that exists on the lookup table and not in the fact table by the use of the 'Preserve all lookup table elements' VLDB property. CAUSE: By checking the SQL statements of the report, there is no "sum" or "group by" statement. Grouping. Open the VLDB Properties Editor this way. For use cases, examples, sample code, and other information on every VLDB property. This query does not return all desired elements of category from the Data Warehouse. x mixed case columns names for a DB2 database by default have SQL generated with quote characters enclosing the name . While the default values should result in the best report performance in most cases, some reports may perform better when certain VLDB Properties are set to non-default values. Without this option all reports would execute their SQL pass by pass in a sequential order over a single database connection. `Temporary view` intermediate table type VLDB settings is not applied in MicroStrategy when using Warehouse Partition Mapping Table. Syntax. 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. Attribute level: Select the desired join behavior for this attribute. Apply Functions provide the capability for MicroStrategy customers to leverage functions specific to RDBMS but not standard in MicroStrategy. Navigate to Tools > Advanced Settings > VLDB Properties to open the VLDB properties editor. For more information, see Simple vs. Select the Security Filters tab. Attribute form expressions must be rendered into SQL and cannot use any MicroStrategy functions specific to the Analytical Engine. This article describes how to show distinct total value via setting distinct subtotal with across level in Microstrategy Developer. There is no VLDB setting associated with this option. 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. This setting provides two options - 'Permanent table' or 'True temporary table'. The SUM() function, like other aggregate functions, is typically used with the GROUP BY clause. Governor. The RANK function is closely related to other OLAP functions. CAUSE: MicroStrategy can support multiple (more than 5) pre-statements to put in a report. 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. By default, the Sum function will be used. so that SQL generated for one report can be manipulated separately from the SQL generated for a different report. First, consider a simple example that we used above to see the working of the SUM() function. `Temporary view` intermediate table type VLDB settings is not applied in MicroStrategy when using Warehouse Partition Mapping Table. Change the VLDB property 'Subtotals over consolidations compatibility ' from the default to: Evaluate subtotals over consolidation elements only (behavior for 7. The Engine generates multi-pass SQL against the ORDER_FACT table and first retrieves the SUM (ORDER_AMT) at the level. It is used to insert any single-value, database-specific functions and simple operators directly into SQL. For more information on the SUM() function, you can read this complete explanation of the SQL SUM() function. The post-execution SQL that was available in Narrowcast can be replaced by implementing post-report SQL VLDB properties. The VLDB property's behavior will be demonstrated using the following attribute and report. Case() and CaseV() functions are Analytical Engine functions, i. A human reader can see from the ApplySimple SQL string that the revenue value will be returned (meaning that the datatype should be Float). This section includes the following. The attribute uses a CASE statement to replace NULL values with -999. . 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. Use Count (Attribute@ID) to calculate total element number (uses count distinct if necessary) For Tandem databases, the default is Use ODBC Cursor. ; Distinct is a TRUE/FALSE parameter that allows you to. 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. . If not, the permanent table’s option is the default setting. Metric with an IF Function. select a11. on how division by zero is handled and can cause failures when your queries use features like indexed views, computed columns or XML methods. Enable Set Operator Optimization (if supported by database and [Sub Query. 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. 82K KB11125: How to control the join order of metrics in the final pass when using the "Do. SELECT SUM(DISTINCT salary) AS "Total Salary" FROM employees WHERE salary > 25000; If there were two salaries of. The formula of a simple metric is based on group functions (such as sum or average). 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. The attribute uses a CASE statement to replace NULL values with -999. 3. Simple metrics always contain at least one aggregate function, such as sum or average, applied to a fact. This VLDB setting is located in the 'Indexing' folder and has the following options:The 'Create Individual Index' VLDB setting was introduced in MicroStrategy 8. Apply (Pass-Through) Functions MicroStrategy Apply. 4. The following steps describes how to create such derived metric. This version of the product is no longer supported in accordance with MicroStrategy's support lifecycle. Use of M03 in Microsoft SQL Server 2000 would result in DATEADD (DD, (1 - DAY (GetDate ())), GetDate ()). 6. The Moving Sum function returns a cumulative total of values based on a specified window size. 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. For more information on the SUM() function, you can read this complete explanation of the SQL SUM() function. A base formula does not have dimensionality (see. If parentheses are required in the database syntax, it is the user's responsibility to provide them, e. MicroStrategy value prompts do not allow multiple values. Reuses redundant SQL. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. 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 hierarchy, or order of precedence, for VLDB properties is outlined in the. sum. In this case, as noted by the text [An Analytical SQL], the functions Trunc and Sum are computed by the Intelligence Server. x. You can use them in many different capacities, which include, creating or modifying both schema and user objects. Specifies that SUM returns the sum of unique values. Instead, it. It is a new feature in. This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. Wherever you can define an expression, you can use a function. There is no VLDB setting. In MicroStrategy, SQL Global Optimization reduces the total number of SQL passes with the following optimizations: Eliminates unused SQL passes, e. There is no VLDB setting associated with this option. 0, a VLDB property is available to control. They can also help you take more advantage of the data. Syntax. The impact is limited to MicroStrategy Command Manager 9. This technical note outlines an issue where certain database-instance level VLDB properties are not being applied to the SQL Engine. ; Distinct is a TRUE/FALSE parameter that allows you to. VLDB Function. 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. This setting provides two options - 'Permanent table' or 'True temporary table'. create /* Table Qualifier */ table /*Table. After a report is run, we keep the connection open (DB connection timeout values apply). The first four statement VLDB properties,. There is no VLDB setting associated with this option. g. 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.