KB39998: Multiple database processes are observed on the Database Server when running a large report against Microsoft SQL Server n MicroStrategy Developer

SYMPTOM:
When running a large report in Strategy Developer against SQL Server , multiple database processes are observed on Database Server monitor.  
 
STEPS TO REPRODUCE:

1. Create a report that have multiple attributes and metrics in order to keep it running for a few minutes.
2. During the execution of report, check the Active Monitor in the Microsoft SQL Server Management Studio, there are multiple processes spawned as shown below: 

 
 
CAUSE:
 
This is an expected behavior with SQL Server and it is similar with the database such as Teradata or Netezza which will spilt up the operation of a query across multiple processes (AMPs for Teradata and SPIs for Netezza). Actually, the same behavior will be observed if the SQL statements are executed directly under Microsoft SQL Server Management Studio. 
For Strategy product, it is working as expected that not more than one MJMULPRC_32.EXE (or MJMULPRC_64.EXE) in the task manager is spawned on the Intelligence Server machine representing only one physical connection to warehouse.
Sometimes this can be reduced on the Database side by changing the max degree of parallelism to be one less than the total CPU.
 
ACTION:
 
It is an expected behavior and there is no action needed in Strategy side. Consult DBA for further assistance.
 
 
Third Party Software Installation:
WARNING:
 
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.