Skip to content

considerations-for-replaying-traces-sql-server-profiler.md

Latest commit

 

History

History
42 lines (31 loc) · 2.41 KB

considerations-for-replaying-traces-sql-server-profiler.md

File metadata and controls

42 lines (31 loc) · 2.41 KB
title Considerations for Replaying Traces
titleSuffix SQL Server Profiler
description Find out which operations, stored procedures, templates, and log activities prevent SQL Server Profiler from replaying traces.
author rwestMSFT
ms.author randolphwest
ms.date 06/05/2025
ms.service sql
ms.subservice profiler
ms.topic concept-article
ms.collection
data-tools

Considerations for replaying traces (SQL Server Profiler)

[!INCLUDE SQL Server Azure SQL Managed Instance]

[!INCLUDE ssSqlProfiler] can't replay the following kinds of traces:

  • Traces that contain transactional replication and other transaction log activity. These events are skipped. Other types of replication don't mark the transaction log so they aren't affected.

  • Traces that contain operations that involve globally unique identifiers (GUID). These events will be skipped.

  • Traces that contain operations on text, ntext, and image columns involving the bcp utility, the BULK INSERT, READTEXT, WRITETEXT, and UPDATETEXT statements, and full-text operations. These events are skipped.

  • Traces that contain session binding: sp_getbindtoken and sp_bindsession system stored procedures. These events are skipped.

If you don't use the preconfigured replay template (TSQL_Replay), and don't capture all required data, [!INCLUDE ssSqlProfiler] doesn't replay the trace. For more information, see Replay Requirements.

For information about what permissions are required to replay a trace, see Permissions required to run SQL Server Profiler.

Related content