A feature is available in the Strategy SQL engine: "Maximum Parallel Queries Per Report." This is a governing setting to control the number of parallel database connections allowed per the feature "Parallel Query Execution" explained in KB44052 for a single report.
In order to adjust the Maximum Parallel Queries Per Report VLDB Property, follow the steps below:
1. Open the Strategy Project Configuration window for the Project you wish to modify. Select 'Advanced,' then 'Configure' under the Analytical engine VLDB properties section:
2. Open the Query Optimizations folder, then select 'Maximum Parallel Queries Per Report:
3. Uncheck the box for 'Use default inherited value,' then adjust the number as desired. (The default is 2, which added to the initial query = 3 total maximum parallel queries.)
The 'Maximum Parallel Queries Per Report' VLDB property setting controls the number of SQL passes that can execute in parallel. Since each pass opens a separate connection (thread) to the database, this setting should indirectly dictate the number of concurrently busy DB threads for that report.
There are several reasons that the number of connections visible in Database Connections System Monitor would not correspond to the number of threads in the setting. When a thread wants a connection, it can either use a cached connection or make a new one. It makes no difference to the Query Engine but will appear different in the connection monitor. Also, the set maximum for parallel queries may never be hit if the SQL runs very fast, since, by the time a certain later pass would be started, the 1st pass may have already finished.
For details on setting the number of connection threads at the Server level, refer to the following Strategy Knowledge Base articles:
KB414567
