The error appears for such a brief period of time I can't ever do any troubleshooting while it exists. Service packs and MDAC are up to date and 98% of...

We've gotten this error about 30 times today, it's getting pretty bad. If anyone can help out I'd appreciate it. I ran SQL Profiler and it appears that when this...

What information do I need to give in order to make it easier to diagnose?

By the way, when I use LIKE I get worse performance than using charindex('searchstring', column) > 0 - Has anyone else noticed this?

I have a variation to this issue, in that I need to go backwards through the items, i.e. start from the bottom and work my way up since results from...

We've actually already done that to prevent problems when a firewall is between the web and database servers...

Interesting.. We've actually scheduled nightly log truncations to keep the log file below the 10 MB limit.. It would get upward of 5 gigs inside of a week or two...

The 30 second timeout is the default command timeout - that you can change via ADO or .NET depending upon what you're using. Why it's taking so long sometimes and...

I used the suggested solution and it worked great. The last post isn't actually a problem since the numbers being updated are unique.

I don't see anything other than sleeping processes for that database. Would I have to do the sp_who2 right after the error occurs or would it stay in that state...

Oh sweet, that makes sense. If that works that will be perfect. I'll post a message saying if it works or not. Thanks!

This is exactly my issue, the clustered index is on the identity column, but the column I am updating is not the identity column but it does have a non...

This is a database issue, the OLEDB provider returns this error - I've been programming for about 6 or 7 years so I know the diff btw a script timeout...