Attribute to Join When Key From Neither Side can be Supported by the Other Side

The Attribute to join when key from neither side can be supported by the other side is an advanced property that is hidden by default. For information on how to display this property, see Viewing and Changing Advanced VLDB Properties.

This VLDB property becomes obsolete when you change your Data Engine version to 2021 or above. See KB484738 for more information.

This VLDB property determines how MicroStrategy joins tables with common columns. The options for this property are:

• Join common key on both sides (default): Joins on tables only use columns that are in each table, and are also keys for each table.
• Join common attributes (reduced) on both sides: Joins between tables use all common attribute columns to perform the join. This functionality can be helpful in a couple of different scenarios.
• You have two different tables named Table1 and Table2. Both tables share 3 ID columns for Year, Month, and Date along with other columns of data. Table1 uses Year, Month, and Date as keys while Table2 uses only Year and Month as keys. Since the ID column for Date is not a key for Table2, you must set this option to include Day to join the tables along with Year and Month.
• You have a table named Table1 that includes the columns for the attributes Quarter, Month of Year, and Month. Since Month is a child of Quarter and Month of Year, its ID column is used as the key for Table1. There is also a temporary table named TempTable that includes the columns for the attributes Quarter, Month of Year, and Year, using all three ID columns as keys of the table. It is not possible to join Table1 and TempTable unless you set this option because they do not share any common keys. If you set this option, Table1 and TempTable can join on the common attributes Quarter and Month of Year.

Levels at Which You Can Set This

Database instance, report, and template