3D Visualization of Server Farm Performance
One picture tells it all. In one 3D graph, view and compare the performance of hundreds of servers with customizable viewing of multiple performance counters or metrics.

Server Farm Health Tree
Fast access to the health of the database server farm with visual indicators of good or poor health. Point and click access to a server. Side by side server comparisons of performance may be viewed. 250+ servers may be monitored.

Dashboards and Cockpits by Server
View a database server’s Big Picture performance profile with a dashboard and cockpit graphical view of the most critical performance metrics for a server. When a performance counter or metric indicates poor performance, double click on the graph point and the SQL (from our ZERO impact SQL capture) that ran during that time period will be immediately displayed.

Historical Baseline Comparisons
Compare the performance of multiple database servers in 3D graphs. Or for a specific database server compare its performance to a baseline.

Product does not use ineffective SQL sampling techniques or traces for the capture of SQL activity. These monitoring approaches may miss most of the SQL activity or place up to a 25% overhead on the database server. Product non-intrusively captures 100% of the SQL activity with zero impact.

Real-time and Historical Custom Graphs
Graphically view SQL and any performance metrics in real-time or reconstruct what occurred for any prior time period. Customize a graph with any combination of performance counters and metrics including the SQL that ran over the time period of interest.

Zero Impact SQL Capture and Monitoring
Non-intrusive ZERO impact SQL capture of 100% of the SQL activity 24x7. Ineffective SQL sampling and intrusive server traces are not used. Allows you to graphically drill down to the exact SQL statements that ran when end-user response time was poor, CPU usage or disk usage are high, or when any performance counter or metric was poor. Since 80% of database performance issues are due to poor performing SQL, being able to reconstruct the exact SQL that ran when performance was poor is an absolute necessity.