Sql server profiler where is it

Click here to read more about the acquisition. Try Our Free Code Profiler. Try Our Code Profiler. By Role. By Technology. By Language. Documentation Support Ideas Portal Menu. Start Free Trial. There are different predefine templates such as T-SQL, Tuning or you can select the standard default template or start from scratch by selecting the Blank template:. Figure 4 — General tab of the Trace Properties form. In the Events Selection tab, you can select all events that you need to include in the trace, not that you can add some filters.

As an example, if you need only to trace the operations executed in a specific database, then you can add a filter on the database name property. Figure 5 — Events selection tab of the Trace Properties from. SQL Server Profiler can be used to detect what are the commands executed by an application over a database for security and tuning purposes. To read more about this tool, you can refer to the official documentation.

This tool takes a profiler trace as input. It gives some recommendations missing indexes, partitioning, etc. To read more about this tool, you can refer to the official documentation: Database Engine Tuning Advisor.

When you access the official documentation , you will see that SQL Server Profiler for Database Engine is deprecated and it might be removed in a future version. With that information, I can verify my thinking and if something seems off I know where I should start looking at the problem. This provides you a live view into what's happening in a live environment, which is mostly undebuggable otherwise. Because you can see the invoked SQL code of the environment, it can help you to spot the cause of a bug.

I'm not saying this solves everything but if you know the application's codebase well, it gives you a starting point to fix that bug as soon as possible. From my experience, the culprit at those moments is usually a bad-performing query. If you remember my setup to start the SQL Profiler, you know that we can take a look at the different parameters, most importantly, the duration of a query and the number of reads it takes to execute the query.

If one of those parameters, or both, are high, it's probably a sign that the query could be rewritten in a better, faster way. Once a query is rewritten, the SQL Profiler can also be used compared with the previous version. Or worse, a bug in your code. Any additional feedback? Skip Submit. Submit and view feedback for This product This page. View all page feedback.