New answers tagged profiler
The tool you want is Express Profiler Small, lightweight SQL profiler, open source, works great with SQL Express. (I am thrilled to have found it!) http://expressprofiler.codeplex.com/
Not a huge fan of reporting profiler for checking blocking, but to get proper analysis would suggest you to either: 1) Use Adam Mechanic's SP_WHOisActive which is indeed very simple way of analyzing what and where could the blocking be a scenario with detailing on database name, app name along with its process. 2) If possible you can use SqlDiag utility to ...
Both of these are user processes and are part of an application, you can check the outer query for the cursor with the following SELECT , c.session_id , c.properties , c.creation_time , c.is_open , t.text FROM sys.dm_exec_cursors (0) c CROSS APPLY sys.dm_exec_sql_text (c.sql_handle) t and the text for the sp_LogPurge with ...
If you are using a database you created via Options and Tools it could be the database is not at a compatibility version that ClearTrace needs. I would suggest letting it create a new database, as doing this I generally never experience issues.
It seems to be that the Options dialogue is for the database that ClearTrace uses to store its own application data. I created a dedicated database for it and it added its own tables to that database, during the 'upgrade'.
Top 50 recent answers are included