| |
Below you'll find various screenshots which give you an insight in how the ORM Profiler GUI offers you the wealth of information it gathers
from the profiled application. Please click on the images to view the image in full size. As ORM Profiler displays
numeric values with the regional settings of the logged-in user, the screenshots show numeric values using the European formatting,
which means the ',' you see in numbers is the decimal symbol.
Main GUI overview screenshots
The user-interface consists of two parts (bottom half with detail views, and top half with grid/tree like data views),
which are kept in sync when you switch between views.
The real-time view offers aggregated data in graph form so spikes in activity can be noticed easily.
One of the views on the profiling data offered by the ORM Profiler client application is Queries in Context,
where each query is grouped below the stack trace of the method which executed the query.
Another view on the profiling data offered by the ORM Profiler client application
is the Connection in Chronological Order. For each connection, this view shows you all open and close actions,
begin transaction, commit/rollback transaction as well as the
queries executed over each connection and within each transaction. If a connection had multiple open / close actions, these are all shown below
the connection.
ORM profiler offers the ability
to obtain the exact execution plan of a SQL statement from the RDBMS itself and shows this information in detailed form with the query.
Query parameter overview with pre/post query execution values per parameter
The general statistics overview of the selected query.
The general statistics overview of the selected connection
The general statistics overview of the selected connection usage period. A connection usage period is the period between a
connection Open and connection Close action. A connection can have multiple connection usage periods
The general statistics overview of the selected transaction
The information available for a selected stack frame in the Queries In Context overview. If applicable, navigation buttons
are enabled to quickly jump to the file location in visual studio from where the call was made.
Buy now!
|
|