Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Enable/Disable Logging of Specific Error Codes Expand / Collapse
Author
Message
Posted Monday, March 24, 2014 10:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 24, 2014 4:29 PM
Points: 2, Visits: 3
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
Post #1554115
Posted Monday, March 24, 2014 12:24 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 3,995, Visits: 7,172
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; They'll drag you down to their level and beat you with experience"
Post #1554185
Posted Monday, March 24, 2014 1:05 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 24, 2014 4:29 PM
Points: 2, Visits: 3
When I execute the following command:
SELECT * FROM SYS.MESSAGES where message_id = 463

I receive the following:

message_id language_id severity is_event_logged text
463 1033 16 0 Functions 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.
Post #1554197
Posted Monday, March 24, 2014 1:34 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 5:46 AM
Points: 3,995, Visits: 7,172
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; They'll drag you down to their level and beat you with experience"
Post #1554204
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse