The VLDB Property, “Cartesian Join Governing," is exempt in the three business cases described below. This means it will execute the Cross Join even though Cartesian Join Governing is set to Cancel Execution.
When the VLDB Property, Preserve all lookup table elements is set to Preserve lookup tables joined to final pass result table, there might be a Cross Join between two Lookup tables, and is exempted from the Cartesian Join Governing VLDB Property.
The following is an example SQL Statement:
The grand total metric is defined as Sum(Cost){}. When the grand total metric and another metric exists on a grid, Cross Join is produced to join to grand total metric and is exempted from the Cartesian Join Governing property.
The following is an example SQL Statement:
When the VLDB Property, Downward Outer Join Option, is set to Preserve all the rows for metrics higher than template level (with report filter or without report filter), cross join will be generated between the higher-than-template-level metric pass and the lookup table(s) for the attribute(s) included in the report level dimensionality but not present in the metric's dimensionality, and is exempted from the Cartesian Join Governing VLDB Property.
The following shows the SQL statement for a sample report with metrics M01, M02 at report level and Units_Sold_at_Subcategory at higher than report level, and metric join type for the metrics set to be Outer Join.
