Starting, Pausing, and Stopping Traces
After you have defined a new trace or created a template by using SQL Server Profiler, you can start, pause, or stop capturing data by using the new trace definition or template.
When you start a trace and the defined source is an instance of the SQL Server Database Engine or Analysis Services, SQL Server creates a queue that provides a temporary holding place for captured server events.
When you use SQL Server Profiler to access SQL Trace, a new trace window opens (if one is not already open) when a trace is started, and data is immediately captured.
When you use Transact-SQL system stored procedures to access SQL Trace, you must start a trace every time an instance of SQL Server starts for data to be captured. When a trace has been started, you can modify only the name of the trace.
When working with existing traces, you can view the properties, but you cannot modify the properties. To modify the properties, stop or pause the trace.
When you pause a trace, you prevent event data from being captured until the trace is restarted. Restarting a trace lets trace operations resume. No previously captured data is lost after a restart. When the trace is restarted, data capturing resumes from that point onward. While a trace is paused, you can change the name, events, columns, and filters. However, you cannot change the destinations to which you are sending the trace data, nor change the server connection.
Stopping a trace stops data from being captured. After a trace is stopped, it cannot be restarted without losing previously captured data, unless the data has been captured to a trace file or trace table. You can also save the collected data to a table or file after stopping a trace. All trace properties that were previously selected are preserved when a trace is stopped. When a trace is stopped, you can change the name, events, columns, and filters.