I was thinking that would likely do it but wondering if that timeout entry in the ODBC DNS string would just apply to the initial DB connection. In which case it likely wouldn't help as the connection to the DB works fine. Its the query timeout that would be the issue. Perhaps there is a separate entry for that in the DNS string or perhaps the timeout entry applies to both. Anybody know for sure??
-----Original Message----- From: Dirk Bulinckx <[EMAIL PROTECTED]> Date: Aug 4, 2005 11:40 AM Subject: RE: [SA-list] database timeout setting To: [email protected] As we're using ODBC for this, I think it's a setting that is within the ODBC applet of the control panel. Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim A Sent: Thursday, August 04, 2005 5:33 PM To: [email protected] Subject: [SA-list] database timeout setting Is there a registry entry to change the timeout for database inserts for statistical or interchange data logging? The reason being is that we've found that everytime our database needs to grow in size the inserts fail because its taking just a little longer than the 30 seconds default timeout to grow the database. ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
