KB17183: Join 89 versus Join 92: Join 89 limitations in MicroStrategy

Strategy provides users with the option to set whether to use Join 89 or Join 92 to generate their reports. For further information on how to set this preference in Strategy the main characteristics, refer to the following Strategy Knowledge Base Article:
 
KB17183: Join 89 versus Join 92: Join 89 limitations in MicroStrategy 8.x  
 
Join 89 was the earlier standard wherein the joins are performed in the WHERE clause.
 
Join 92 is the later standard wherein the joins are performed in the FROM clause.
 
Limitations:

1. With Join 89, a table could not be outer-joined to more than one other table. It would result in the ORA-01417 error. The following Strategy Knowledge Base technical note describes this error:
    
   
2. KB11739: "ORA-01417" error message appears when attempting to run the out-of-the-box "30.1 Queue Time Breakdown" report in MicroStrategy Enterprise Manager 9.x against an Oracle 9i database.

Since Oracle 8i only supported Join 89, Strategy Technical Support found one instance wherein this turned out to be a limitation with the Strategy Enterprise Manager data load not transferring data completely for child reports within documents. The new Strategy Enterprise Manager data load scripts (for Oracle 9i and above) use Join 92 such that this limitation is avoided. The following Strategy Knowledge Base technical note describes this Oracle specific problem:
 
KB11530 (KB6400-75x-0317): Child reports within HTML documents that hit the cache are not counted correctly in Strategy Enterprise Manager 7.5.x against the Oracle Enterprise Manager warehouse
 

• The lack of precedence of filter condition before join condition in some situations - for instance, if the joins occurred in the WHERE clause before the filter condition (such as WHERE Column1 = xyz or WHERE Column1 IN (xyz, abc)...) - could affect performance depending on the size of the tables involved. This is avoided using Join 92 since the joins are performed in the FROM clause.