KB40533: Query Band statement to the secondary instance in a multisource environment, the query band does not take effect in MicroStrategy Developer 9.x and 10.x

SYMPTOM:
When users apply a Query Band statement to the secondary instance in a multisource environment, the query band does not take effect in Strategy Developer 9.x and 10.x
 
Example:
When using the below query band example in a report pre-sql in a secondary database instance VLDB properties, nothing happens when running a report.
 

SET QUERY_BAND = 'ApplicationName=Strategy; ClientUser=!u; Source=PLM; Action=!o;' FOR SESSION;

 
 

However when switching the database instance to the primary one it appears in the report as follows:

SET QUERY_BAND = 'ApplicationName=Strategy; ClientUser=Administrator; Source=PLM ; Action=Program Review Milestones;' FOR SESSION;

 
CAUSE:
This is working by design.
Certain VLDB properties exist at the database instance level but are viewed by the engine as database unrelated properties. This includes pre/post statements for reports. This means that Strategy only looks at the project's primary database instance for reading these properties.
 
ACTION:
This enhancement has been implemented in Strategy version 10.7. Please upgrade to this version to take advantage of this new feature.