Considerations for replaying traces (SQL Server Profiler)

Applies to: SQL Server Azure SQL Managed Instance

SQL Server Profiler 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, SQL Server Profiler 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

• bcp Utility
• SQL Server Event Class Reference
• sp_getbindtoken
• sp_bindsession
• BULK INSERT (Transact-SQL)
• READTEXT (Transact-SQL)
• WRITETEXT (Transact-SQL)
• UPDATETEXT (Transact-SQL)