In some situations, multi-threading database connections may lead to instability in the environment. This article reviews how to disable the multi-threading of database connections using ODBC or OLE DB connections to test whether this provides more stability or not.
When running things with the EnableParallelReload set to a value of 1, the database connections may multi-thread, which will utilize more CPU cores than if the connections are single-threaded with the value of 0, which can cause stability issues if the server does not have many CPU cores in it but has many concurrent tasks. Using the 0 setting will force single-thread condition, thus each reload process will only use a single CPU core for any database connections.
For Publisher/QlikView Distribution Service
The path to the correct Settings.ini file is: C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch\
Add the EnableParallelReload=0 setting under the [Settings 7] section and save the file, the QVB processes will run as a single-thread process regarding database connections. There is no need to restart any services after adding this, as the QVB processes are spawned on demand and they read the Settings.ini for each new process spawned.
For QlikView Desktop
Settings dialog method:
- Open the Desktop client
- Click on Help menu
- Click About option
- Right click the product logo in the lower left corner of the resulting dialog
- In the Settings dialog, scroll to "EnableParallelReload" setting and left click
- In the Value block, change the Value to 0 from the default of 1
- Click the Set button
- Click the Close button
- Close the About QlikView dialog and run reload again
To make the change directly in the Settings.ini for the Desktop client:
- Use Windows File Browser to browse to: C:\Users\UserProfile\AppData\Roaming\QlikTech\QlikView
- Open the Settings.ini file
- Add the EnableParallelReload=0 setting under the [Settings 7] section
- Save the file
- Reopen the Desktop client and test