Are the commands still actually timing out? If so, you could have a problem in your commands themselves. I would consider two things:
1. Are the commands causing some sort of deadlock? 2. If you are transactional, are you exceeding the size of the log? Rob -----Original Message----- From: Arif [mailto:[EMAIL PROTECTED] Sent: Saturday, July 26, 2003 10:30 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] "Timeout expired. The timeout period elapsed prior to completion of I am gettting the timeout error when trying to run a large number of update statements within ADO.NET. I tried increasing all of the timeouts in SQLServer (e.g. 'remote login', 'query wait' etc. and also the connection and query command timeouts on the client within ADO.NET but the problems is still there. To give more details, let's say I want to do 10,000 updates in a for loop. Running the sql profiler, I notice that the code works fine and update e.g. 200 to 300 updates but after that it just hang. Nothing happen. Any advise would be highly appreciated. Thanks Arif
