| title | Considerations for Replaying Traces |
|---|---|
| titleSuffix | SQL Server Profiler |
| ms.prod | sql |
| ms.prod_service | sql-tools |
| ms.reviewer | |
| ms.technology | profiler |
| ms.topic | conceptual |
| ms.assetid | 73fa339f-b71a-4be4-97ca-d4ae84c8b90b |
| author | markingmyname |
| ms.author | maghan |
| ms.custom | seo-lt-2019 |
| ms.date | 03/06/2017 |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] [!INCLUDEssSqlProfiler] cannot replay the following kinds of traces:
-
Traces that contain transactional replication and other transaction log activity. These events are skipped. Other types of replication do not mark the transaction log so they are not 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.
Note
If you do not use the preconfigured replay template (TSQL_Replay), and do not capture all required data, [!INCLUDEssSqlProfiler] does not 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.
bcp Utility
SQL Server Event Class Reference
sp_getbindtoken (Transact-SQL)
sp_bindsession (Transact-SQL)
BULK INSERT (Transact-SQL)
READTEXT (Transact-SQL)
WRITETEXT (Transact-SQL)
UPDATETEXT (Transact-SQL)