dbForge Event Profiler for SQL Server
Capture and analyse SQL Server events
Description
A page stalls for fifteen seconds now and then, the application log says only "query timeout", and which statement ran, with what parameters and for how long, is anyone's guess. Microsoft deprecated its own SQL Server Profiler years ago and recent SSMS builds no longer ship it. dbForge Event Profiler fills that gap: connect to an instance, pick a predefined template, and it records the stored procedure calls, T-SQL batches and transactions happening inside the database engine, each with its full statement, duration, read and write counts and the login that issued it.
Before tracing you choose which event classes to capture, which columns to keep and what filters to apply, for example only statements over 500 milliseconds or only one database, so a few minutes do not produce hundreds of thousands of rows. Traces are written to local files for later reading or for sharing with a colleague.
It is a free Devart tool and a standalone application rather than an SSMS add-in, which keeps it usable now that new SSMS builds no longer include Profiler. DBAs use it to chase performance problems and developers to see the SQL their application actually sends.
Event tracing: Captures stored procedures, T-SQL batches and transactions from the database engine with full statements and context.
Predefined templates: Standard templates cover common investigations, so tracing starts without ticking event classes one by one.
Event and column filters: Filter by event class, column and condition to keep the trace file free of noise.
Performance analysis: See which statement costs the most time, reads or writes, to pin down slow queries and blocking.
Trace files: Write a session to disk with size limits and file rollover for offline analysis.
Multiple connections: Trace several configured SQL Server instances, each with its own connection.
Standalone: A separate application rather than an SSMS add-in, still usable now that SSMS drops Profiler.
Before tracing you choose which event classes to capture, which columns to keep and what filters to apply, for example only statements over 500 milliseconds or only one database, so a few minutes do not produce hundreds of thousands of rows. Traces are written to local files for later reading or for sharing with a colleague.
It is a free Devart tool and a standalone application rather than an SSMS add-in, which keeps it usable now that new SSMS builds no longer include Profiler. DBAs use it to chase performance problems and developers to see the SQL their application actually sends.
Features
Event tracing: Captures stored procedures, T-SQL batches and transactions from the database engine with full statements and context.
Predefined templates: Standard templates cover common investigations, so tracing starts without ticking event classes one by one.
Event and column filters: Filter by event class, column and condition to keep the trace file free of noise.
Performance analysis: See which statement costs the most time, reads or writes, to pin down slow queries and blocking.
Trace files: Write a session to disk with size limits and file rollover for offline analysis.
Multiple connections: Trace several configured SQL Server instances, each with its own connection.
Standalone: A separate application rather than an SSMS add-in, still usable now that SSMS drops Profiler.
