Events
31 Mar, 11 pm - 2 Apr, 11 pm
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to:
SQL Server
Azure SQL Managed Instance
Pausing a trace prevents further event data from being captured until the trace is restarted.
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.
Select a window that contains a running trace.
On the File menu, click Pause Trace.
Events
31 Mar, 11 pm - 2 Apr, 11 pm
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayTraining
Module
Manage and monitor data warehouse activities in Azure Synapse Analytics - Training
Manage and monitor data warehouse activities in Azure Synapse Analytics
Documentation
Create a Transact-SQL Script for Running a Trace - SQL Server Profiler
Find out how to create a Transact-SQL script from an existing trace file or table in SQL Server Profiler.
Run a Trace After It Has Been Paused or Stopped - SQL Server Profiler
Find out how to start capturing event data again after a trace has been paused or stopped in SQL Server Profiler.
Close a Trace Window - SQL Server Profiler
Discover how to close the trace window in SQL Server Profiler that captures event data. Learn how to close it either during the trace or after it has finished.