Every now and then I work with people that just use the default trace templates available within SQL Server Profiler. Using the default traces and you end up being limited to just some performance stats on procedures and batches that have completed. There isn’t exactly an issue with doing this, except that there is so much more that can be done with Profiler.
For instance have you ever needed to do any of the following?
- Monitor for table/index scans or deadlocks
- Verify that applications were not under reporting errors
- Troubleshoot memory problem
- Check to see if there are any transactions utilizaing deprecated syntax
But how would you find out about doing any of this type of stuff. The place I’d recommend starting is with Mastering SQL Server Profiler by Brad M McGehee (twitter | blog). This book was originally writtern for SQL Server 2005, but it is still very much applicable. And why am I bringing this up today? Well, it was applicable enough for me to send off to a few people this week in response to their questions.