March 24, 2014 at 10:20 am
Hi, All.
I am having an intermittent problem with commands timing out when updating a table. The table is quite small (~1500 records).
My question is: how do I turn on logging of error code 463 (which I think is the error that is occurring) to the ErrorLog, so that I can troubleshoot what's going on?
John Brainerd
March 24, 2014 at 12:24 pm
This should already be automatically logged to the SQL Server Error log. How are you executing this UPDATE statement? If you could, please post the update TSQL and the "time out" error you are receiving.
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 24, 2014 at 1:05 pm
When I execute the following command:
SELECT * FROM SYS.MESSAGES where message_id = 463
I receive the following:
message_idlanguage_idseverityis_event_loggedtext
4631033160Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'.
So, I surmise from this that the 463 errors are not being logged. The error happens within an application, so I can't really exact SQL.
March 24, 2014 at 1:34 pm
If you can't find the error in the SQL Server Error log, I would pretty much guarantee that it's not SQL Server throwing the error. Sounds more like the "application" is timing out and the error number is related to the application's error reporting.
To find the query, set up a profile trace, using criteria to filter out just your application (this will minimize load on your SQL Server).
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply