The most recent content from our members.
Time flies when you were having fun, so I must be having a blast because Database Performance Analyzer 10.2 has arrived in a blink of an eye (just 6 months since 10.1). If you are ready, you can download it from the customer portal and for free evaluation from the SolarWinds Website. Be prepared to save hours every day as…
DPA currently polls the database and gathers information about long running queries. Queries that run quickly but then hold locks are not identified as problems, and the SQL text of the queries is not available. The result is that the SQL for a victim of a deadlock situation or idle blocker situation can be seen in the…
As shown on this screen, SPID 122 was an idle blocker: For the SPID being blocked, there is a value in the SQL column. Of course, there is not one for SPID 122 because by definition, there is no active SQL for it. However, it would be very useful to have a link with text similar to "Most recent SQL for this session" that…
I would like to be able to click on the 122 in the following screen and have it take me to the detail page for the SPID for this same date and time selection: Instead, I now have to click on the Sessions tab, and then visually attempt to find 122 in the list of sessions on this screen: The SPID numbers are not searchable…
I see the following in Ignite: The top line shows SPID 91 as a head blocker with the notation "idle blocker", blocking SPID 179. How can I find what is causing the blocking? In line 5, SPID 91 is again shown as a head blocker, this time with the notation "blocker" and the full details that I need to diagnose the situation.…
It looks like you're new here. Sign in or register to get started.