SYMPTOM:
In a Strategy project using multisourcing, users may note that the VLDB property "Metric Join Type" for the primary database Instance is set to Outer Join. However the VLDB property of "Metric Join Type" for the auxiliary database Instance is set to Inner join.
When a report is executed from this project that uses only the auxiliary database instance, the SQL generated by the Engine will be seen to ignore the Metric Join Type setting for the auxiliary database instance - instead the primary database Instance Metric Join Type setting (Outer Join in this case) will be used.
CAUSE:
The observed behavior is the expected behavior.
Certain VLDB properties exist at the database instance level but are viewed by the SQL Engine as unrelated to the database used. This set of unrelated VLDB properties includes the Metric Join Type setting. These settings are passed to the specific report/job VLDB properties only from the project primary database instance. This means that Strategy SQL Engine only looks at the project's primary database instance for reading these properties and in determining the SQL to generate.
ACTION:
There is an enhancement request to enable these properties to be read from the auxiliary database instance if the dataset only uses that instance.
Refer to the Technical Document below for another database unrelated VLDB property “pre/post statements for reports”:
KB40533 -- Query Band statement to the secondary instance in a multi source environment, the query band does not take effect in Strategy Developer
