Comments
2 comments
-
Hi
I've ran a trace on one of my servers, and yes SQL Monitor seems to be creating a lot of user error messages like the following:
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Changed database context to '<DatabaseName>'.
It suprises me that they are classified as 'errors' as it sounds more like 'information' to me. Running a simple USE statement in Management Studio also creates one of these errors so I don't think we're doing anything particularly wrong. Just doing it a lot!
It'd be interesting to hear any opinions about this. I'll keep investigating.
Regards
Chris -
I'll see if there is any way to disable these by trace flags.
Add comment
Please sign in to leave a comment.
The Application name was "SQL Monitor - Monitoring - GUID HERE".
The BatchStarting was:
Which generated a "User Error Message"
Also, there are:
Which generated a "User Error Message" with the value "Changed database context to 'tempdb'."
There seems to be a lot of these initiated by the "SQL Monitor - Monitoring - GUID HERE" application.