The first step in monitoring SQL Server with SQL Server Profiler is to create a trace and filters. This will allow you to choose what gets monitored. When defining a trace you can specify the following items:
- A name for the trace
- Whether or not the trace is runable by other users
- The event classes that you want to trace
- The information to track for the events
- How to filter the events
- Where to store the traced information
When filtering events, you can pick any data column and assign values to include and values to exclude. In most cases, you will want to make your filter as restricted as possible, otherwise you will see lots of events traced. This can make it harder to troubleshoot problems.