SQL Server Profiler Tips-filtering requests

　　

　　

If you need to reprint, please attach the author and the original link: http://www.cnblogs.com/zeusro/p/4016228.html

Microsoft SQL Server Profiler is a graphical user interface for SQL tracing that is used to monitor the database engine or instances of analysis Services. You can capture data about each event and save it to a file or table for later analysis. For example, you can monitor your production environment to see which stored procedures affect performance because of slow execution.

　　 To run SQL Server Profiler, use theStartmenu, point to"All Programs"、Microsoft SQL Server 2008And"Performance Tools", and then click SQL Server Profiler.

In the new tracking template selection of the default standard for me is enough, event selection, the individual is so selected. That is, the reply event, the stored procedure, TSQL.

But this is not enough, in the beginning of monitoring there will be a lot of interference, as SSMs sent a request, Report server sent a request. And I just want to monitor the SQL generated by LINQ in the program. Of course can use Linqer, but with this software when I solve the problem of permissions, run time or error, so give up.

Back to the point, the solution is the column filter in the diagram above. One feature of the request from EF is that ApplicationName is always entityframework, so set it as a rule to add "like" to ApplicationName joins. The same is true of other screening criteria.

Also note that this property can only be changed without monitoring, at run time to stop after changing the property.

SQL Server Profiler Tips-filtering requests