ID, SERVICE_TYPE. For this example, assume we have a order_fact table has two dates, order_date and ship_date and an invoice_fact table with two dates invoice_date and actual_ship_date. An outer join means return all rows from one table. Given a choice, it is recommended to use a JOIN over a sub query. x with the date attribute filtering on an aggregate from base derived metric gets ignored in a Dossier/VI Dashboard when attribute join behavior is set to Outer Join To Lookup. In the following example, we will join emp and dept tables using joiner transformation in. This will return all the elements present in the lookup table even if they don't exist in the fact table. This will help authors of dossiers embed workflows that provide consumers with options for guided analyses. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformHow to Define Join Behavior. Our vision is to enable Intelligence Everywhere. How to use Guacamole to copy and paste text or files in MicroStrategy on AWS; All new Download site is now available!Community & Support Search Discussions Open A Case View My CasesFull Outer Join not returning unmatched join field values SQL SERVER 2005. In short, an inner join includes only data that is common to all components of the join. Go to Tools and enable Show Advanced Settings. For example: Metric (Default Inner Join):But I think MS SQL engine some how using table inserts to workaround it to complete half outer joins, but not full outer joins. CUSTOMER_ID (+); Now, I have created an attribute called customer Id at MSTR and defined the join (Through checking the box). This article notes how to setup Ranking for metrics that do not return data for all attribute elementsfrom Full Outer Join( Ex14_tempcube2, Full Outer Join( Ex14_tempcube1, Ex14_tempcube0 ) on DA3 ) on DA1 to RELATION15-<DA5, DA2, DA3, DA1, Prev Month Id, Month Of Year> Cause: This is a known issue in MicroStrategy. Watch free 3-5 minutes tutorial videos, with subtitles available in 9 languages, to build product fluency! Start learning. All rows of the intermediate table are preserved. Shared attributes are outer joined while relationships control other related attributes. 0 MicroStrategy releases. There's a reason we're at the top of the list. Issue with full outer join in SQL Server. The SQL FULL OUTER JOIN statement joins two tables based on a common column. KB221464: The report SQL does not generate outer join due to one metric been mistaken as a nested aggregation metric in MicroStrategy Analytics Developer 10. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. 11 and earlier releases. It is denoted by symbol θ. 1. Join queries. BakkerJoop. Joint child relationships are really another type of many-to-many relationship where one attribute has a many-to-many relationship to two otherwise unrelated attributes. Great idea, but does not work! From a no apparent reason, no metric dimensioned in MicroStrategy can be “conducting”, ie standing in a LEFT OUTER JOIN on the left side. Join common attributes (reduced) on both sides. In the same pass and between 2 different tables. The following examples show how datasets are joined. The join types for a metric base formula are as follows: A default join is a join that is. Date functions specific to different databases (YTD) transmutations lacking using transformation. Inner and outer joins are discussed with examples. From what you have described an outer join on the metrics seems to be the right thing to do. This article will provide a full overview, with examples of the SQL Outer join, including the full, right and left outer join as well as cover the union between SQL left and right outer joins. Join common key on both sides. mstr file can be opened in MicroStrategy Desktop and MicroStrategy Workstation. For example, setting Metric Join type to "Outer" at the report level (Metric editor > Tool > Metric Join Type) overwrites the Metric Join Type set at the Database Instance Level: The subject of Outer Joins is a very broad one, however, as a continuation of. Another way is to use the Lowest level attribute in the report object pane. ( How?) Expand Database instances. Example 1: Same attributes in both datasets, different metric, and same filter (same element values). Steps to reproduce This example uses the MicroStrategy Tutorial warehouse that is shipped with MicroStrategy. Click Demo. Starting MicroStrategy 11. For example, tutorial datasets may contain unrelated attributes and cross join metric values rather than joining the metric values. Select Support. For more details on enabling the setting, refer to Change Data Engine Version After the fix, metric outer join works and data returns. 9. For these databases, MicroStrategy implements a technique of analyzing each metric's result pass to obtain all the distinct attribute elements that are required to preserve the rows. On the duplicated visualization, go to Metric Options and change outer join for both the metrics to be inner join. 11, analysts can now add direct links within a dossier. Full Outer Join Support: Support: Select/Insert: Bulk Insert String ; Select/Insert: UNION Multiple INSERT: Use UNION: Select/Insert: Distinct / Group By option: Use DISTINCT: Query Optimizations. • Other pages within the. For attributes, the default join type is the outer join. How to use an outer join to retrieve data when a metric on the report has a condition that is mutually exclusive with the report filter in MicroStrategy 10. Sorted by: 2. In MicroStrategy SDK 9. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. column_name; 3. 0, a VLDB property is available to control. If the join type is changed, the SQL statements would also change. xWhy MicroStrategy Why MicroStrategy; Customer Stories; PlatformNote: In MicroStrategy 11. The following settings are advanced properties which are hidden by default: Full Outer Join Support. To change the lookup table from 'LU_COUNTRY' to 'LU_REGION' (for example), click on 'Modify' in the Form definition section. You are returned to the Project Configuration Editor. Share. Then, this document. Create another logical table (or view) for your prices: Full Outer Join Support: Support: Select/Insert: Bulk Insert String ; Select/Insert: UNION Multiple INSERT: Use UNION: Select/Insert: Distinct / Group By option: Use DISTINCT: Query Optimizations: Sub Query Type: Use temporary table; falling back to IN (SELECT col) for correlated subquery: Query Optimizations: SQL Global Optimization Click the Joins folder to expand it and then choose Full Outer Join Support. Scenario 2. 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. Discussion around the uses of full outer joins. Move the new Modified New Dossier back to the original location. mstr file is actually a . The key thing is, MS uses the exact opposite concept from the database outer join - I am not sure why, but say metric A you need for sure, metric B is optional, you need to set metric A as OUTER JOIN metric,. from master_dimension m left outer join sub_dimension sub on m. Contrast this with an inner join. Note that if there are other metrics on the report whose report level metric join type is set to 'inner join,' the report SQL will reflect inner joins and left outer joins depending on the reporting scenario. On the duplicated visualization, go to Metric Options and change outer join for both the metrics to be inner join. Full Outer Join Support is an advanced property that is. 9. A. FULL OUTER JOIN. Connecting. 7. In order to resolve this issue using MicroStrategy, I enabled the VLDB property- ‘Cartesian Join Warning’ to ‘Execute’. If this choice is selected at attribute level, it will be treated as preserve common elements (that is, choice 1) optionA metric join setting determines how data is combined by applying a specific type of join, inner or outer. How to use an outer join to retrieve data when a metric on the report has a condition that is mutually exclusive with the report filter in MicroStrategy 10. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties. UNPIVOT. 4. Full outer join: Performs a full outer join on the columns. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. The "Downward Outer Join" VLDB property allows higher-level metrics to be outer joined by constructing a table of all necessary attribute elements to be included early in the join path. Linked attributes appear with a Link icon in the Datasets panel. Perform a left outer join first to keep all attribute elements at the Store, Day, and Item level, then aggregate the data to the Store and Month level. MicroStrategy Intelligence Server uses an ODBC Call (SQLDescribeCol) to determine the proper resources to allocate for the query results for VARCHAR columns this will lead to performance degradation. 2/7/2019 3:34:07 PM select * from Left Outer Join. Set the Attribute Join Behavior to "Outer Join - Preserve Filter" 4. The following descriptions use an example of a report containing the Region attribute, the Sales metric, and the Budget. This should happen only if you use the first approach. Execute a report. VLDB properties can provide support for unique configurations. This defect is addressed in MicroStrategy 11. select a. If the parent report is configured, under Report Data Options > Attribute Join Type, to preserve all lookup table elements joined to the final result table, then the target report will also preserve lookup table elements. Options for the VLDB property, Attribute to Join When Key From Neither Side can be Supported by the Other Side, can no longer be selected once you upgrade your data engine version to 2021. Specifically if a metric at a higher level is set to outer join while a lower level metric is set to inner join while both include an attribute the lower level metrics version of the attribute will be used to join to lookup tables despite being less complete. I want to query so I can get the SERVICE_TYPE_TEXT from the first table that matches the ID given in the second. 6. Having the following hierarchy: Country > Distribution Center > Calling Center > Full Outer Join Support is an advanced property that is hidden by default. CREATE TABLE fruits ( fruit_id INTEGER PRIMARY KEY , fruit_name. 29K. Login MicroStrategy. The options for this property are No support Support, which assumes that. A join clause in the Structured Query Language combines columns from one or more tables into a new table. 52K KB440718: Aggregate from base derived metric with an attribute to ignore filter does not get ignored in the metric calcula… Select VLDB Properties from the Data menu to access the VLDB Properties (Report) dialog box. Steps are as below. Each basket stores zero or more fruits and each fruit can be stored in zero or one basket. The fourth row gets the rank 4 because the RANK() function skips the rank 3. In MicroStrategy 10. The Project-Level Very Large Database (VLDB) Property setting, found in Joins > Preserve All Lookup Table Elements, 'Preserve lookup table elements joined to final pass result table based on template attributes with filter' is not turned on, which results in. Cross joins appear when two tables do not have any common key attributes between them in which they can inner join. This is to support the most common scenarios for your databases. LEFT JOIN; RIGHT JOIN; FULL JOIN; 1. All report metrics use outer join: No flags are generated. 4. However, enabling full outer join support for specific reports is recommended if full outer joins are only used for a small to moderate amount of reporting needs. You want to place metrics on the report and make the join types Outer Join. key) ) = little. SQL Global Optimization; Metric Join Type; Steps to Reproduce. A simple idea would be to modify the metric by means of dimensionality, namely, the LEFT OUTER JOIN attributes with the setting ignore add / None. The setting can be found under the Advanced tab. Example. ttl_qty, b. Step 3) Type the query in the query editor: SELECT Book. And once again I had to annoy me about the fact that there is no clever way to MicroStrategy, an outer join between the attributes to be generated. To understand Downward Outer Join, consider the following report that contains the attribute Store and two metrics, Sales Per Store (M1). Result: Acts as one dataset. Preserve All Final Pass Result Elements. In this case, Promotion has a many-to-many relationship to both Item and Quarter. SQL FULL OUTER JOIN is used to retrieve all records from both joined tables left table and right table, it combine the functionality of left outer join and right outer join. Do perform outer join on nested aggregation when all formulas have the same level: If all the inner metrics have the same level, which is lower than the report level, and the formula join type for the outer metric is set to outer, then an outer join is performed on the. Two other VLDB properties, Downward Outer Join Option and Preserve All Lookup Table Elements, have an option to apply the filter. Number of Views 3. Here are the different types of the JOINs in SQL: (INNER) JOIN: Returns records that have matching values in both tables. so_no, b. Rows containing values for inner join metrics but not the outer join metric are dropped. 33 Responses to “Handling Conditions on Outer Joins”. SELECT col1, col2, col3…. The SQL passes will then left outer join and give you the results you want. Result: Acts mostly as one dataset, but missing values are. MicroStrategy is the leading enterprise business intelligence tool with its mission statement to make every enterprise a more intelligent enterprise. e. 1 or above, to pick up the fix, enable project level setting "Data Engine Version" to 11. 1. Instead, it creates two passes of SQL and creates all SQL correctly except without an outer join to the lookup table in the final pass. x, outer joins are designed to get all the data from the lookup tables. ( How?) Expand Database instances. An inner join is a standard type of join. The customers with cust_id “3” have no orders, and the orders with order_id “103” has an id order and no matching customer, so their respective columns contain NULL values in the result. To Create an Intelligent Cube Using Freeform SQL or Query Builder. If there's no matching row, return null. Downward Outer Join Option is an advanced property that is hidden by default. A SQL statement joins back to the lookup table when using a logical view to create an outer join between attributes in MicroStrategy SQL Generation Engine. Database instance, report. The MicroStrategy SQL Generation Engine uses the COALESCE function to ensure correctness and consistency in full outer join results. Create three reports named A (with attribute A), A&B (with attribute A and B),A&C (with attribute A and C) Create a dashboard based on the three reports created in last step. Solution: This issue has been addressed in MicroStrategy 2021. MicroStrategy Engine provides the capability to switch the order of. mstr suffix. Companies of all sizes use this platform to assess, visualise, and build dashboards. In the Tutorial project, the user needs to create a report, for. All articles. To support this capability, the Analytical Engine behavior with respect to join data from multiple datasets has an option to control the join behavior between datasets known as 'Join Behavior'. The SQL Engine makes three SQL passes:The following Syntax is for the left outer join. The join type determines what type of join (inner or outer) is used by the SQL Generation Engine for each one of the metrics in a given report. If installed over previous versions of the product, the folder remains the same. BACKGROUND: Theta joins are not supported by MicroStrategy. c1 = t2. The MicroStrategy SQL Engine applies the designated join type to the data pulled from your data source's tables. 4. It selects records that have matching values in these columns and the remaining rows from both of the tables. In LEFT OUTER JOIN, all the values of the columns you select from the left table will be included in the result of the query, so regardless of the value matches the join condition or not, it will be included in. FULL [OUTER] JOIN. 1 release. Click Save and note that the metrics are still outer joined. Create three attributes named A, B, C, and after them added in a report in Developer, no data returns， as showed below. For example: Metric, by default is Inner Join. x releases, and the new Multi-table Data Import (MTDI) cubes. Watch the video below to see some creative use cases and learn how to build! 5 new visualizations unlock meaningful ways to explore your data including Modern Grid, Sankey, Time Series, Multi-Metric KPI,. Here is a sample SQL: SQL BEFORE 11. Theta Join allows you to merge two tables based on the condition represented by theta. A. The operation corresponds to a join operation in relational algebra. Description Starting from MicroStrategy 10. Join Base Table Join for Template = Use Fact Table . By default all the attributes are outer join in report data option. •. There's a reason we're at the top of the list. However, enabling full outer join support for specific reports is recommended if full outer joins are only used for a small to moderate amount of reporting needs. This issue has been addressed in MicroStrategy 2021. Full Outer Join Support is an advanced property that is. 4. In this situation a full outer join is done between the two tables to get a full set of elements of the year_ID attribute . 1. Sub-Queries should only be used as a fallback solution when you cannot use a JOIN operation to achieve the aboveThere's a reason we're at the top of the list. Some report metrics use outer join, and others use inner join: This case is currently not subject to Global Optimization level 3 or 4. Also you can take advantage of Metric Dimensionality i. Join common key on both sides. [CATEGORY_ID])) To be able to view all elements of category, including those from the metric pass that are not present in the Category lookup, the SQL statement needs a left outer join clause. Additional Final Pass Option is an advanced property that is hidden by default. If you created two facts with the condition inside than you don't need the conditional metrics and the outer join –This article describes how SQL Global Optimization handles inner versus outer joins between metrics in MicroStrategy. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. Default Value. Unrelated and nonshared attributes will be cartesian joined. Business users move seamlessly between all five styles of BI and even combine multiple styles. contacttypeid=b. Check Query DetailsThis document describes how to use the Logical View feature introduced in MicroStrategy to specify an outer join between two attribute lookup tables when only attributes are on a report. The Full Outer Join Support setting specifies if the database platform supports full outer join syntax. SQL Full Outer Join. The first pass calculates Sales; the second pass calculates Item Sold. No specific customizations were made for this feature. To be more specific the product creates a metric dataset for the join between datasets and then outer joins that to the. We will learn all JOINS in SQL server with examples: INNER JOIN/simple join. However, Full outer join is not supported when Join Type = 89, so the SQL is generated as inner join when Full outer join type = Yes. Downward Outer Join Option is an advanced property that is hidden by default. x. item_key. Video. On the Freeform Sources tab, select one of the following options: To create an Intelligent Cube by creating SQL statements using the Freeform SQL Editor. Brief instructions are provided using the example below. STEPS TO REPRODUCE: Create a custom group with two rows, region in Canada and region in center; This document describes how to use the Logical View feature introduced in MicroStrategy to specify an outer join between two attribute lookup tables when only attributes are on a report. A metric join setting determines how data is combined by applying a specific type of join, inner or outer. PRIME stands for Parallel Relational In-Memory Engine, and it engulfs two types of in-memory cubes: OLAP cubes, or the traditional Intelligent Cubes that have existed since 9. Brief instructions are provided using the example below. To perform an outer join against a lookup table Open the Project Configuration Editor. Create three reports named A (with attribute A), A&B (with attribute A and B),A&C (with attribute A and C) Create a dashboard based on the three reports created in last step. In order to resolve this issue using MicroStrategy, I enabled the VLDB property- ‘Cartesian Join Warning’ to ‘Execute’. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. 1, it is possible to identify specific attributes as having an incomplete lookup table by setting the “Preserve all final pass result elements” VLDB property within the attribute. OFFSET and FETCH. FROM Customers. id. In this video I will show you how to use VLDB settings to create left outer joins in MicroStrategy. x, once a custom group and a level metric are add into a report, though you enable join type to outer join, null value still can’t been seen. Users can link the dossier to the following elements: • Any external URL. Tip #1: The word ‘ OUTER ‘ is optional. For example, if a report showing your profit data is. To Define a Join Between the Columns of Two Tables. This causes multiple counting in the report level aggregation, and also the discrepancy between the Income Bracket IDs and descriptions. Perform the steps in this article to change the metric join type from the product default (Inner) to Outer for all reports in the project. Go to Metric Options again and note that the metric join still says Outer Join. This will be your lookup table for your Item attribute. MicroStrategy Technical Support can assist with resolving cross joins in a specific report, however caution should be taken when resolving such issues. There's a reason we're at the top of the list. . Two attributes: Parent01 and Child01 have a parent-child relationship. So in 9. These settings affect how MicroStrategy Intelligence Server manages joins, metric calculations, and query optimizations, among other options. Make sure that this attribute is stored at the specific level in the Fact table which you want to join. In terms of join behavior this means the setting applies to metric joins between datasets. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. Note: To create custom expression qualifications, the advanced qualification option must be enabled in the report designer's preferences in MicroStrategy Desktop 8. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. SQL FULL OUTER JOIN example: In this example, the clause returns all rows from both the customers and orders tables. Full Outer Join . After the project information is. DealSizeUnit should be a metric that an attribute. Click OK. You can configure properties such as SQL join types, SQL inserts, table creation, Cartesian join evaluation, check for null values, and so on. Creating a. When talking about Theta joins the following operators are used < , ≤ , > , ≥ , ≠. User can define the inner/outer join behavior through Report Data Option in each individual report. However, in the third pass, when combining the results from the first two passes to generate data for Unit Sales, a full outer join between pass 1 and 2 is performed. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. A simple idea would be to modify the metric by means of dimensionality, namely, the LEFT OUTER JOIN attributes with the setting ignore add / None. This allows the FOJ to be rewritten to a different kind of join in the. This is appropriate if the metric should be outer joined in every circumstance. RIGHT (OUTER) JOIN: Returns all records from the right table, and the matched records from the left table. This article explains how to control the join order of metrics when using downward outer join settings in MicroStrategy. Data Management Programming Tools MicroStrategy, Inc. The MicroStrategy SQL Generation Engine uses the COALESCE function to ensure correctness and consistency in full outer join results. Its not about Outer join between passes. By default, MicroStrategy generates multi-pass SQL using derived tables with Teradata 12 (and higher). ago. Loading × Sorry to interruptA metric join setting determines how data is combined by applying a specific type of join, inner or outer. To add another cube, repeat Steps 4 and 5. 10 it is possible for users to view the query details of a visualization in a dossier. So in 9. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. If a document does not contain any primary datasets, all datasets are joined using inner joins. In full outer join, all records from both the sources are returned. You can right-click the line representing the join and select one of the four join types described above to modify the join type. Why MicroStrategy Why MicroStrategy; Customer Stories; PlatformSimilar to scenario 1, three passes are generated. CustomerID=Orders. This article describes how SQL Global Optimization handles inner versus outer joins between metrics in MicroStrategy. INSERT, UPDATE, and DELETE on Views. A fact extension can be used to relate a fact to an attribute using a fact table. Of course in your case no vehicle is a car and a bus too, so you need to tell MicroStrategy to do an outer joins for the two conditional metrics that you created. Controls whether tables are joined only on the common keys or on all common columns for each table. EQUI JOIN; SELF JOIN; 2. In their own words, “MicroStrategy is the largest independent publicly traded business intelligence (BI) company, with the leading enterprise analytics platform. Community & Support Search Discussions Open A Case View My Cases The problem with your query isn't the use of COALESCE, but simply with the JOIN. zip file, with the. 1K views 3 years ago MicroStrategy In this video I will show you why you need outer joins and how to solve this for multiple scenarios in MicroStrategy using. 1. The MicroStrategy SQL Engine applies the designated join type to the data pulled from your data source's tables. Login MicroStrategy Developer 2. There's a reason we're at the top of the list. The general case of JOIN operation is called a Theta join. SQL Join statement is used to combine data or rows from two or more tables based on a common field between them. This dialog box is accessed from the Advanced Settings option in the Tools menu of the Metric Editor. num. You must have write access to the datasets you intend to link. 4. doc_id = b. This video demonstrates how to create custom SQL filters in MicroStrategy. The join type places conditions on the data to be displayed in the report. ORDER BY. Limitations: With Join 89, a table could not be outer-joined to more than one other table. I also created an additional dummy metric that serves the same purpose as introduction of dummy data within the data warehouse. Join 89 was the earlier standard wherein the joins are performed in the WHERE clause. If two columns both have null values, those columns are not recognized as "Equal". Steps are as below. Attribute to Join When Key From Neither Side can be Supported by the Other Side. Some report metrics use outer join, and others use inner join: This case is currently not subject to Global Optimization level 3 or 4. If two columns both have null values, those columns are not recognized as "Equal". An outer join of A and B gives the results of A union B, i. We can retrieve data from more than one tables using the JOIN statement. This issue has been addressed starting in MicroStrategy 9. You can use. You are not really doing a Cartesian product; you are doing an INNER JOIN. A compound metric contains multiple expressions or metrics. Some report metrics use outer join, and others use inner join: This case is currently not subject to Global Optimization level 3 or 4. Too bad!There's a reason we're at the top of the list. Click Save and note that the metrics are still outer joined. There's a reason we're at the top of the list. 4. •. The table now appears in bold as shown below. x. Great idea, but does not work! From a no apparent reason, no metric dimensioned in MicroStrategy can be “conducting”, ie standing in a LEFT OUTER JOIN on the left side. Support, which assumes that the Join Type VLDB setting is Join 92; any other value in Join Type is ignored. CAUSE: In the example above, the final pass compares End_id of Temptable1 and End_id of Temptable2. CREATE TEMPORARY TABLE. id UNION SELECT * FROM t1 RIGHT JOIN t2 ON t1. Upload FilesOr drop files. Taking the report above as an example, when the grouping for the "Products" user hierarchy is set to "standard", the SQL for the report is as. x. Ranked #1 for Enterprise Analytics in 2022 Gartner Critical Capabilities Report. In short, an inner join includes only the data common to all the elements in the join, whether that data is tables or metrics. x. And I have another attribute called Address from Address table which is straightforward. Select the Cube and click OK. FROM t1 FULL OUTER JOIN t2 ON t1. In this video I discuss when to use joint element lists in MicroStrategy and demonstrate how to create them. In the future, please include the complete table definition in your questions (the CREATE TABLE part). Follow the steps below. txt. In this example, we used an asterisk (*) in the SELECT clause, which is a shorthand for all columns. Full Outer Join Support = Outer-Join . Additional details about each property, including examples where necessary,. 8. UNION. When you specify a table to join with a fact, you are creating a table relation to extend a fact. In the right corner of the dashboard, change the. OrderID. This property can only be enabled through Workstation. Cross Join. I think as Jac74 said i have to work with view or in my case i can add a null row in the the table and use applysimple to convert that null value to some other value like "0" to make a regular inner join. Therefore, SQL is generated for the filtering report using an inner join between the two metrics, and since the metrics have no attribute elements in common, all data are excluded. MicroStrategy uses different defaults for the join type based on the database you are using. 8.