I have recently created a trace within SQL profiler. I am trying to monitor whenevr a TSQL statement is run against a particular database. I have made sure that my filters are correctly defined e.g. the database I'm looking at and the login nae I want to monitor. Whenever I run the trace it also generates other events as well. These events are tied to the administrator account and appear to be generated from the MSDB database. Is there any way to stop these events from appearing as I am having to manually filter through the results to find what I'm looking for. Hope this makes sense. Any help would be most appreciated.
Regards
Regards