[11.3.277 Pro] - BUG: SQL Profiler

[11.3.277 Pro] - BUG: SQL Profiler

There are some critical issues with the SQL Profiler.

#1. Filtering on Login name does not seem to work properly. While it does not show activities that have their login name set to another name, it still shows activities where the login name is empty but it definitely has nothing to do with the login it should filter on.

#2. Further filtering is impossible because it does not even support sorting on the table header (so that at least one would be able to group records by Application/Status/whatever). Quasi-realtime analysis is quite limited, one has to constantly click the Refresh button.

Thank you very much. The first point is a known issue and we are readying a fix for this weekend. there are couple other bugs reported that will be addressed in the next build.

For the second point, the concept is that the profiler's role is mostly helping to create the trace and collect required activities, and make that as simple as possible. After that if there are many activities collected, I would say more then a few dozens, analysing them in a fairly small space isn't ideal. The Export button can be used to export them to a spreadsheet program for extended analysis, filtering, grouping, graphing, whatever may be required.