| title | Start a Trace |
|---|---|
| titleSuffix | SQL Server Profiler |
| ms.prod | sql |
| ms.prod_service | sql-tools |
| ms.reviewer | |
| ms.technology | profiler |
| ms.topic | conceptual |
| ms.assetid | aeeb38eb-229a-4c8b-ad66-57e9ce45fb6a |
| author | markingmyname |
| ms.author | maghan |
| ms.custom | seo-lt-2019 |
| ms.date | 03/14/2017 |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
After you have defined a new trace or created a template by using [!INCLUDEssSqlProfiler], 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 [!INCLUDEssDEnoversion] or [!INCLUDEssASnoversion], [!INCLUDEssNoVersion] creates a queue that provides a temporary holding place for captured server events.
When you use [!INCLUDEssSqlProfiler] 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 [!INCLUDEtsql] system stored procedures to access SQL Trace, you must start a trace every time an instance of [!INCLUDEssNoVersion] starts for data to be captured. When a trace has been started, you can modify only the name of the trace.
Note
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.
Start a Trace Automatically after Connecting to a Server (SQL Server Profiler)
Pause a Trace (SQL Server Profiler)
Stop a Trace (SQL Server Profiler)
Clear a Trace Window (SQL Server Profiler)
Run a Trace After It Has Been Paused or Stopped (SQL Server Profiler)