DBCommandTimeout — Legacy
This documentation is for legacy Kiwi Syslog Server versions 9.8.3 and older.
Use this Kiwi Syslog Server registry setting to specify the timeout value for logging messages to a database.
Section (32-bit Windows OS) | HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds\Syslogd\Properties |
Section (64-bit Windows OS) | HKEY_LOCAL_MACHINE\Software\WOW6432Node\SolarWinds\Syslogd\Properties |
Value (STRING) | DBCommandTimeout |
Min value | 1 |
Max value | 120 |
Default value | 5 |
Type | Seconds |
The Log to Database action uses ADO to insert records into the specified database. By default ADO database commands will timeout after 30 seconds if the database is busy or does not respond.
If you see ADO command timeout errors in the error log, you may want to extend the timeout value. Because the database records are inserted in real time, a long timeout may cause message loss or delay the processing of other messages in the queue. Only extend this timeout if you are experiencing timeout errors.
By default, the database insert command will wait up to 30 seconds before returning a timeout condition. If your database is slow and needs more time to process the data in real-time, you can extend the timeout up to a maximum of 120 seconds. Setting the timeout value to 0 will cause the command to never timeout (this setting is not recommended as it can cause the program to fail if the database does not respond).