Recent Review from Similar Course

"This was my first dba course. The course flowed well and the instructor seemed confident in his knowledge. Instructor stayed on topic and didn't get sidetracked by going down 'rabbit trails' of additional content, which can sometimes happen. I would definitely take another class with the same instructor."  Phil Carpenter 

Microsoft SQL Server Profiler is a graphical user interface to SQL Trace for monitoring T-SQL Statements of Database Engine

SQL Server Profiler is a powerful tool that allows you to capture and analyze events.

This information can be used to identify and troubleshoot many SQL Server-related problems.

One of the things that separate less knowledgeable DBAs from exceptional ones is that exceptional DBAs know how to take full advantage of the tools available to them.

Even though Profiler can be used to monitor analysis services and integration services its core use is for tracking down real world issue that happen within SQL Server’s database engine.

In this course, we are going to cover the architecture of SQL Server Profiler and then use it to track down performance related issues.

In the course, we are also going to cover the nomenclature in detail. What’s an event and for that matter what’s an event class? How do I use them?

The interface isn’t that intuitive and in this course we will walk through all the tabs and their meaning as well as learn how to use them to capture only what we want to see, not the thousands of lines we don’t need.

With profiler, we can: create traces, watch the trace capture the spids in real time, store it, replay and even save the output to a server to others can view the results in table format.

There are several reasons profiler isn’t used more often in the real world. Firstly, the interface isn’t well designed, secondly it creates a ton of data when it’s not filtered and lastly it can consume a lot of resources on the server.

If the profiler is configured appropriately to trace only relevant data for analysis, it will diminish the additional load that is introduced while it is running.

If profiler is run for a longer duration, then to capture the event of longer duration it is very important to collect selective data, otherwise the collected data can outgrow the space on the server.

In this course, we are going to learn how to ameliorate all the “issues” with the tool and learn how to use it effectively in the real world.

Thanks for your interest in Real World SQL Server Profiler.