IN THIS CHAPTER
Viewing SQL Server events
Merging Profiler data with SysMon
I love SQL Server Profiler.
When tuning my own application, or as a consultant when I arrive at a job site, one of the first things I do is to fire up Profiler to capture a full trace of every ad hoc SQL query and stored procedure call. (You can read more about my performance trace in Chapter 64, "Indexing Strategies.")
I use a Dell Latitude E6400 notebook, which is great for traveling, but in the SQL Dungeon (my basement), I attach the notebook to a normal keyboard, a mouse, and a large monitor. The notebook screen becomes a second monitor off to the left. When I code, the second monitor runs Profiler and displays performance stats as I code.
Of all the SQL Server programs and icons, I have only three pinned to my main Start menu: Management Studio, Books Online, and Profiler.
Profiler is to the DBA what a camera is to a photographer. Any photographer who doesn't have an affection for his favorite camera must not be much of a photographer. (I just got a Nikon D60 for my fiftieth birthday!) Likewise, any SQL Server professional needs to be intimately familiar with Profiler. When I help clients by doing tech interviews, I always ask the candidate if he or she loves Profiler. It's one of the mandatory minimum skills.
If you're new to SQL Server, let me introduce you to SQL Server Profiler:
SQL Trace is a lightweight, but powerful, technology that can run on SQL Server; ...