Hi Alex;

  The main thing to remember is that PowerServer's "Connection Pooling" does not work with ODBC connected DBMS. Instead, the Connection Pooling must be done within the ODBC Manager for the related DSN. Otherwise connection pooling could be off for those type of DB connections - even though PS's setting is ON (>0).

  The maximum amount of CP'ing will be related to the maximum number of concurrent App threads you anticipate. The minimum should be set for the expected low thread activity that your PS Apps could have. So say for example 5,000 App users where the low end threads are 0 and the high end is 1,000 - I would suggest MIN 5 and MAX 1000.

HTH

Regards ... Chris

Hi Alex, What database are you using?

Hello Armeen;

ASA (ODBC)

Oracle

SQL Server

Thanks Chris for your answer.
Do you have any comment about SQL Server or Oracle connections?, Does we need to make the "Connection Pooling" configuration in each Database Client or in the Web API PS Solution?

Hi Alex,

Thanks for catching the mistake in the document.  We will update it right away.

Regarding the command timeout settings, please note that we would recommend configuring the timeout values for transaction, session and request in the AppConfig>Application.json file in the ServerAPIs project. It is not best practice to modify the default settings directly in the database.

Best regards, Julie 

Thanks Julie for your kind answer.