CommandTimeout when running Maintain Database Indices Job
Aug 22 2017
Sep 13 2017
Closed, Fixed and tested
With a big and highly fragmented database, the call to the SP can easily take more than 30 seconds.
To address this, a new parameter was added to the Commerce Scheduled Job "Maintain database indexes." The parameter lets you set a maximum number of seconds for which you want the job to run. Previously, the default value of 30 seconds was not adjustable