Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
poole
Starting Member
6 Posts |
 Posted - 2007-01-11 : 04:33:42
|
| new to using the sql profiler, i would like to be able to have the profiler running to trace/record when an error appears in the server logs, i also would like the results to be saved in a table. any advice / tips on how to set this up would be very helpful. i have previously tried but seem to end up with information overload. thanks in advance |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2007-01-11 : 11:54:52
|
| Everything you want to do is supported, just follow the docs to set it up. As long as you put filters on the events and only select the events you want you should be able to keep the amount of data manageable. If you have specific problems setting it up, post those here and I'm sure someone can help. |
 |
|
|
MohammedU
Posting Yak Master
145 Posts |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-01-13 : 22:21:55
|
| I have had problems tracing and looking for certain types of errors. It has never been that big an issue, so I have never tracked down why I was missing certain kinds of errors. Keep that in mind when setting up your trace. You may want to develop a test script that generates the types of errors you are looking for, and then run a test trace to ensure that profiler actually is catching them.btw, what errors are you looking for? -ec |
|
|
|
ForceF16
Starting Member
13 Posts |
|
|
|
|
|
sql profiler