SQL Profiler for SQL Server: Trace, filter, and analyze events

dbForge Event Profiler for SQL Server is a FREE tool that allows you to capture and analyze SQL Server events. Troubleshoot, fine-tune, and optimize your SQL database performance using Event Profiler data. Whether it's high server load or queries slowing down your workflows, Event Profiler will help you identify the issue and plan improvements.

  • View sessions running on servers and the queries they are executing
  • Find out what front-end applications have the heaviest activity
  • Examine statements, batches, and procedures with poor performance
  • Detect the queries that impact server productivity the most
  • Monitor, trace, and investigate user activity for audit purposes
  • Track the impact of users on SQL Server resource utilization
  • Identify the users responsible for particular activities on the server
  • Trace the activity of SQL Server Database Engine

Features

Predefined Profiler templates

Choose from the four available template categories to set up event tracing according to your project needs:

  • Locks and Blocks: Count the number of locks per query and identify the most lock-intensive queries.
  • Query Execution: Understand the query execution flow and trace errors back to specific queries.
  • System Monitoring: Track the activity of your system and monitor server connections and log files.
  • Trace System: Capture the behavior of SQL statements and stored procedures as they are executed.

Use the Standard template to apply default settings and capture the largest number of events.

Keep track of all the previous actions, stored procedures, and T-SQL batches from your past sessions.

Get free tool

SQL Server events to capture

Choose from dozens of categories of SQL Server events to create the most relevant event profile of your database behavior:

  • General events
  • Events related to query execution
  • Errors
  • Warnings
  • Events related to memory usage
  • ...and many more

Use the default event capture settings corresponding to the selected template or customize them as necessary.

Get free tool

Actions and global fields

Select the actions (global fields) to be captured in the event session:

  • Names, IDs, and addresses related to your database, client, server, or session
  • Task elapsed time
  • Errors
  • Call stacks
  • Other SQL actions and fields

Adjust the list of actions as required by your project or use the default settings corresponding to the template.

Get free tool

Advanced event filters

Fine-tune your profiling by specifying the criteria by which events should or should not be included:

Choose 'All' Operators for the bigger range or go with any particular option:

  • Operator, such as NOT, AND, OR, AND NOT, and OR NOT
  • Event, for example, Login, Logout, Existing Connection, etc.
  • Global fields related to the selected event
  • Comparator defining the comparison of the event field value to the pattern
  • Pattern representing a filtering condition

Group and sort your filters for better visibility and enable and disable them as necessary.

Get free tool

Profile parameters and columns

Select the columns you want to capture in the profile session for each event you selected in the Event Filter:

  • Existing Connection
  • Login
  • Logout
  • RPC Completed
  • SQL Batch Completed
  • SQL Batch Starting

Customize the list of columns as necessary by adding and removing them one by one or in bulk. Reorder the list according to your preferences or reset it to the default values.

Get free tool

Server Profile document and analysis

Review and analyze your SQL event profile in a Server Profile document listing the traced events matching the criteria and filters you specified:

  • Filter the results by one or more parameters
  • View event details
  • Extract the event SQL statement into an SQL window or to the clipboard
  • Navigate the database in Database Explorer
Get free tool

Still using the standard SQL Server Profiler? See why our tool is way better:

1500+ traceable events

1500+ traceable events

dbForge Event Profiler captures all the possible types of events to fit in a single document with all the details for future audit and analysis.
Higher tracer performance

Higher tracer performance

Now it takes seconds to load the largest of databases that pop up immediately in the final document overview as well as to launch the tool.
Lower traceable server load

Lower traceable server load

Well-tailored code structure makes up for a concise server interaction, drastically reducing the stress weighed upon the server during the events.
Flexible events filter

Flexible events filter

The Event Filter can be set up based on the Operator, Event, Source, Comparator, Pattern, and the custom parameters or go with "all" events for the overview.
Useful grid with sorting

Useful grid with sorting

Fast and easy data sorting with a simple header shortcut click. Holding SHIFT enables secondary sorting up to as many column sortings as you wish.
Query syntax highlighting

Query syntax highlighting

SQL convenience the way you like it - each SQL query has its text highlighted to distinguish SQL statements, operators, and clauses from the other text.

Get more free SQL Server tools

dbForge

SQL Decryptor

dbForge SQL Decryptor

Decrypt encrypted stored procedures, views, triggers, and functions in SQL Server

Download for free
dbForge

Monitor

dbForge Event profiler

An add-in for SSMS that allows you to track and tune SQL Server performance

Download for free
dbForge
Search
dbForge Search

Locate database objects and table data across your databases directly in SSMS

Download for free

Leading companies choose dbForge SQL Tools

Berkley
Arconic
Polaris
Jabil
Hewlett Packard Enterprise
Lam Research
Microsoft

Frequently asked questions

What problems does Event Profiler for SQL Server solve in daily DBA work?

Event Profiler helps database administrators identify performance bottlenecks, such as inefficient queries, locking, blocks, and other issues. With Event Profiler, it is much easier to debug queries and stored procedures, monitor user activity, and diagnose application slowdowns.

When should I choose dbForge Event Profiler over SQL Server Profiler?

While Microsoft SQL Server Profiler is an effective tool for detecting and troubleshooting SQL Server issues, dbForge Event Profiler can be a more optimal choice if you are looking for an integrated solution with extensive functionality. Being a part of the dbForge ecosystem, Event Profiler ensures seamless integration with other database management tools, thus allowing you to quickly resolve performance issues by fine-tuning SQL queries or optimizing execution plans. In addition, a wide selection of events, filters, and fields supported by Event Profiler enables accurate event tracing even in large datasets.

Can I run Event Profiler on production without adding heavy overhead?

It is not recommended to run Event Profiler on production due to the overhead it may create on the workload. However, if absolutely necessary, you can reduce it by configuring the tool to only capture necessary event data, limiting the tracing time, and monitoring the server performance to make sure that tracing does not affect response times.

How do predefined templates speed up SQL Server Event Profiler setup?

Predefined templates include default settings of the events to capture and actions, which eliminates the need to configure them manually. However, you can still customize these settings according to your goals.

Which events are the most useful for diagnosing slow queries and blocking?

To identify issues that slow down or block SQL queries, try tracing the following events:

  • RPC Completed and SQL Batch Completed to capture execution details of queries and stored procedures and identify slow ones.
  • Lock Deadlock and Lock Deadlock Chain to find deadlocks that cause queries to fail.
  • Blocked Process Report to identify and diagnose blocked processes.
  • Attention to catch a cancel operation, a client-interrupt request, or a broken client connection.
How do event filters in dbForge cut noise compared with SQL Server Profiler?

By supporting predefined templates and filters, dbForge Event Profiler delivers cleaner and more precise results, filtering out unnecessary system chatter. SQL Server Profiler, in its default configuration, has no such feature.

What is the best workflow to capture, save, and replay a trace?

dbForge Event Profiler for SQL Server supports the complete event tracing workflow:

  • Set up event tracing by selecting the events to be captured, setting filters, and configuring the inclusion criteria.
  • Run the trace and capture data.
  • Save the data in the predefined location.
  • Replay the trace to reproduce issues and find improvement options.
How does Event Profiler for SQL Server support auditing, security reviews, and compliance?

By capturing user activity data, such as login and logout events, permission changes, and schema updates, Event Profiler supports security audits and reviews and helps maintain compliance. SQL query capture allows tracking data access and manipulation. The Server Profile document generated by Event Profiler contains data required for audits and regulatory reviews.

Where do Extended Events fit - do I still need a GUI profiler like dbForge?

No, you do not strictly need dbForge to use Extended Events; however, it makes working with this feature much easier. dbForge Event Profiler provides a number of predefined templates and filters that accelerate the configuration of event traces. With the customization and filtering options supported by Event Profiler, you can set up event tracing focused on relevant data and reduce noise.

What SQL Server permissions, storage, and retention practices should I follow for traces?

To use Event Profiler, you need the following permissions:

  • ALTER TRACE
  • ALTER ANY EVENT SESSION
  • CONNECT SQL
  • VIEW SERVER STATE TO

Control the storage space used by trace files by limiting the maximum file size and enabling file rollover. These settings are available on the General tab of the Profile Server Events wizard.

Retain trace files as long as necessary for troubleshooting or analysis. If longer storage is required for compliance, archive trace files to reduce the storage space.