SalvageDog (2/1/2011)

---

Hello,

Thanks for a great article.

I have a very intermittent problem, occurs only two or three times a month. Would there be any issues with running a server side trace all day, other than creating a lot of .trc files? I'm especially concerned about an all-day trace using too many resources and affecting server performance.

rob mcnicol (1/31/2011)

---

great article, thanks.

what tweaks to this process are required to run a server-side trace on analysis services? when i export my Script Trace Definition, the 'For SQL...' options are greyed out. i am only able to export 'For Analysis Services...' which produces an xmla file.

what do i do with that xmla file to schedule the trace?

rob mcnicol (2/1/2011)

---

i subsequently found this:

http://www.sqlservercentral.com/articles/Profiler/63097/

the summary answer to my question is: paste the xmla code into a job step

thanks again

rob

ejavier.r.dk (5/9/2011)

---

great article. for a very very basic sql user like me, this is great!

Now, I want to use the info from the trace in SCOM, and I know SCOM can read logs. but would it be possible to somehow add a logic that would generate a NT log event when queries take longer than x ms?

Then the scom side would just have to catch that event in the nt log.

Thank you in advamce