Cost Threshold for Parallelism
We are in the process of upgrading our Pega DB SQL Servers from v2012 to v2016. The System DBAs involved in the SQL upgrade process have asked what is the Pega recommended value for ‘Cost Threshold for Parallelism’? In our current production (which is in SQL 2012 version), this value is currently set to 5. However, as part of the lower test environments migration/upgrade the DBAs have set the ‘Cost Threshold for Parallelism’ to 50. Posting this query here to understand if PEGA recommends any specific value for this? Is 50 a safe value?
NOTE - Current Pega Platform version is 7.4. Soon the Pega application will also be upgraded to Pega 8.5.2, after SQL Server 2016 goes live.
Ford Motor Company
US
@SANJEEBAN Pega wouldn't recommend any specific number for this specific setting. However, your DBA should set the number based on the Parellalisam activity happening on the DB Server. If the DB Historical waits pointers to Parellalisam , you should increase the number.
I've Pega 7 and 8 apps running on SQL Server having Parellalisam from 5 to 150 , depending on the load and the capacity of the Server.
Atos UK
GB
Thank you @SUMAN_GUMUDAVELLY for your response.
This is helpful. I will discuss this with our System DBAs.