One of our sites has an intermittent SQL Server timeout error. The error is infrequent, I'd say it happens two or three times a week, and this is on a site that only has a few users (literally). Sometimes the timeout occurs when trying to select data from the DB (SQL Server 2000, running on Windows Server 2003) but sometimes it happens when simply trying to open a connection.
Here is the error that happened early this morning, for example:
Microsoft OLE DB Provider for ODBC Drivers
[Microsoft][ODBC SQL Server Driver]Timeout expired
I found the following article and implemented the recommended hotfix from Microsoft:
http://support.microsoft.com/kb/957585
However, I am uncertain how to proceed from here. How do I use the BID trace points the article mentions? I can't seem to find much information about this. I had assumed I might find something in Windows Event Viewer or in the 500 error page when the timeout happens. However, nothing seems to be different.
My questions are:
1) How do I use the BID trace points, specifically how do I access any log data they generate when the ODBC timeout error occurs?
and/or
2) Is there another method I can use to diagnose the problem? That might even be preferable if this BID trace point business is complex. :)
Note: I know that switching to OLE DB might stop the error from happening. Unfortunately, the site uses quite a lot of stored procedures. I would need to set nocount on for most of those stored procedures, since they return data, and I'd prefer to avoid having to go through the entire site to do that.
Thank you in advance.