Documentation / Trace Replay / Tips & Troubleshooting

Tips & Troubleshooting — Trace Replay

Azure SQL Managed Instance

The tool automatically detects Azure MI (Engine Edition = 8) and:

  • Hides the local file target option
  • Shows the Azure Blob Storage URL field
  • Displays an informational banner about MI limitations
  • Defaults to ring_buffer storage

Tips for Azure MI

  • ring_buffer size: Increase to 128+ MB for heavy workloads
  • Azure Blob Storage: Recommended for production-level capture volumes

Command-Line Arguments

DBLenseTraceReplay.exe [-s server] [-u user] [-p password] [-e]
ArgDescription
-s, --serverSource server name
-u, --userSQL login username
-p, --passwordSQL login password
-eUse Windows Authentication

Troubleshooting

IssueSolution
"Cannot create event session"Ensure you have ALTER ANY EVENT SESSION permission
No events capturedCheck the database filter; ensure workload is running
Azure MI file target errorUse ring_buffer or Azure Blob Storage URL
High error count during replayCheck target database exists; verify permissions; increase command timeout
Missing events in ring_bufferring_buffer has size limits; increase buffer or use file/blob target

System Requirements

ComponentRequirement
OSWindows 10/11 or Windows Server 2016+
Runtime.NET 8.0 (or self-contained package)
SQL ServerSQL Server 2012+ (for Extended Events)
AzureAzure SQL Managed Instance (fully supported)
PermissionsALTER ANY EVENT SESSION on source; appropriate permissions on target
InstallationNone — single portable .exe