The Case of the SQL Stored Procedure Slowdown

Featured Editorials (Feb 21 2012)

1. 

   The combination of Prelert's advanced analytics and correlation capabilities with CA Introscope rich monitoring capabilities let users cut the time to finding the root cause of issues by 90%.  In a recent example, an Introscope administrator was trying to resolve an issue, in an unfamiliar application, resulting in a slowdown in a SQL stored procedure (> 200 seconds).

   The Introscope system was monitoring over 2700 unique metrics.  Prelert had narrowed this down to 24 metrics, which were directly related to the issue. Prelert's Activity View is a scrolling time window that allows the user to scroll back in time, prior to an event, to investigate other anomalous activities. Using Activity View the administrator was able to identify MQ and application slowdowns 10 minutes prior, all related to a specific ‘action’ being called 5 minutes prior to that. 

   The administrator was then quickly able to get very specific performance information to the correct application support team for a quick resolution.  Additionally, the administrator was now armed with the metrics for MQ, application and SQL that he could set thresholds for so that he could be quickly alerted in the future if a similar scenario took place in the application.

    

    

   Bookmark or Share this article