Page History
...
| Tip |
|---|
You can use the History Browser to view past performance and go back to the point in time to view the sessions involved with the blocking alerts you receive. |
Navigate through the blocking tree to find sessions that cause blocks, and then either trace sessions to find out what is causing the blocks or stop the session to have it removed. To trace a blocked session or lead blocker select it from the list and click Trace Session. To stop a blocked session, or lead blocker, select it from the list, and click Kill Session.
| Tip |
|---|
Deadlocks have no lead blockers and are circular in nature. For this reason, SQL Diagnostic Manager does not display deadlocks in the Blocking Tree but does display instances of deadlocks in the Blocking Chart. In addition, SQL Diagnostic Manager does not count self-blocking sessions as blocked or blocking sessions. |
...
The Blocking Sessions Report (Block Reports) displays blocking and blocked sessions’ information (Click image to view full size). To access the Blocking Sessions Report in the Alert view, select the Show Block Details option in the right-click context menu. You can also access the same information on the Blocking View by selecting a specific SQL Server instance, pointing to Sessions, and then selecting the Blocking ribbon.
...
The Deadlock Sessions Report (Deadlock Reports) displays deadlock sessions information (Click image to view full size) . To access the Deadlock Sessions Report in the Alert view, select the Show Block Details option in the right-click context menu. You can also access the same information on the Blocking View by selecting a specific SQL Server instance, pointing to Sessions, and then selecting the Blocking ribbon.
...
| Tip |
|---|
To retrieve the deadlock sessions report for SQL Diagnostic Manager, select the "Non-Query activities>Capture deadlocks (SQL 2005+)" check box in the Activity Monitor Tab. |