Database Timeouts

Hi Everyone,

As you may know all databases queries (like, Insert, Update, Delete, Select) should have timeout to prevent deadlock and prevent over-usage of hardware resources.

Database Timeouts

In Acumatica we have 2 timeout for Select query:

  1. Report Timeout – is used only for reports, as it may need some time to retrieve data from database for big report. To configure it you can use reportQueryTimeout=”100″ in PXSqlDatabaseProvider section of Web.config file. Parameter is defined in seconds and has default value as 30 seconds. You can read more here.
  2. Querry Timeout – is used only for inquires and other selects, as some inquiries also might take more time than allowed by default. To configure it you can use queryTimeout=”100″ in PXSqlDatabaseProvider section of Web.config file. Parameter is defined in seconds and has default value as 30 seconds. You can read more here.

For performance and deadlock-protection reasons Acumatica does not have general timeout configurations for Insert/Update/Delete, however you can change it from code using PXCommandScope (read more here). If you create that scope and change timeout, than next SQL command will be executed with your timeout.

Have a nice queries!

3 Replies to “Database Timeouts”

  1. Hello

    I create sales order but show this error

    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    How to solved this, I can not create or delete the data

    1. Hi Dedi,
      I recommend you to create a support case with Acumatica Support, so we can check that is happening. It is not normal to have timeout on the sales order creation.

      1. Hi Sir, may I also know the reason of this “Execution Timeout Expired” Error, in our case its mostly happen in OTC transaction.

Leave a Reply

Your email address will not be published. Required fields are marked *