Comments
2 comments
-
This is because your SQL Server's error log is long. Response needs to read the errorlog to look for various things. The only way to do this is sp_readerrorlog which reads the entire log every time - Response then ignores everything it saw before and looks at the remainder.
The way to avoid this would be to have a job that calls "sp_cycle_errorlog" periodically (e.g. daily - depending on how fast it grows). -
Thanks Nigel. I was seeing the same problems with 46 occurrences in the last hour alone. This may be a useful bit of information in the help file, or perhaps to add an alert/recommendation that the log file is getting to be too long.
Add comment
Please sign in to leave a comment.
I like the product, it is working well, however I have a query that SQL Response raised about itself:
Long running query:
sql response: xp_readerrorlog
Has anyone else experienced this, and what could be causing it?