I came across an interesting scenario last week, someone needed to trace statements and they didn’t have SQL Profiler installed. Turns out they don’t actually need SQL Profiler in order to trace the statements hitting the instance. There is a trace flag (4032) that can be used to trace statements. When used with 3605, you can have all the statements written to the error log for review.
I played around a bit with getting this working and found a few things that were interesting enough for a geek like me. So I made a video, it’s just under 3 minutes long:
If you happen to be one of those persons that needs to do some tracing but don’t have SQL Profiler handy, you may still be able to get the job done.