Benefit from detailed wait-event analysis and optimized performance
See your enterprise at a glance. Quickly identify the cause of performance deviations, along with any changes to your SQL Server environment.
Create customized dashboards and reports through a powerful enterprise administration and alerting interface. Plus, automate and track performance-tuning and problem-resolution initiatives. Get a wealth of information — through context-sensitive advisories and detailed wait-event analysis — at a fraction of the impact of conventional collection methods.Note: The functionality of Foglight Performance Analysis for SQL Server is now included in Foglight for SQL Server.
- StealthCollect® – Reduce overhead with deep SQL-level collection and analysis.
- Context-sensitive advisories – Maximize performance with built-in analytics and business intelligence that allows you to review workload data and generate customized reports.
- True time-sensitive baselines – Quickly identify out-of-bounds activity with the IntelliProfile® learning baseline algorithm.
- Historical lock analysis – Receive historical reviews of blocking-lock scenarios to speed resolution of SQL Server concurrency issues.
- Statement-level wait-event analysis – Solve resource-related performance issues faster with wait-event data down to the statement level.
- QuickCompare – Swiftly determine the causes and symptoms of performance deviations in application environments, and take immediate action.
- Automated change tracking – Get customized alerts about changes to server, instance, database and schema environments, as well as application SQL degradations.
- Integrated reporting – Define, customize, generate, schedule and deliver targeted, built-in reports on a variety of topics and data points – such as system health, performance, trends and changes.
- Long-term performance repository – Get dimensional analysis in a relational SQL Server database, as well as unlimited performance and environment data storage.
|Platform||Pentium III (Pentium IV recommended) or compatible processor|
|Hard Disk Space||450 MB of disk space required for a full installation, which includes 200 MB download of temporary setup files that can be removed at the completion of the installation|
Notes: The disk space required may vary based on options selected for installation
Database files extracted from a backup require additional storage space depending on the size of the database
|Microsoft Data Access Components (MDAC)||Version 2.6 or later installed. To verify the MDAC version installed on your computer, follow the instructions from Microsoft's website:|
|CPU, Memory, and Hard Disk Space||According to the Hardware requirements document accessible from the Documentation page on the Performance Analysis web site|
|PeopleSoft Versions||8.0 or later|
|Microsoft Data Access Components (MDAC)||Version 2.6 or later installed. To verify the MDAC version installed on your computer, follow the instructions from Microsoft's web site:|
- US English
Performance - SQL
At a glance, get visibility into all the SQL running in your environment to pinpoint troublesome queries and poorly performing applications.
History - Summary
Identify SQL Server instance workload, including information on which resources are being used, information on Windows host health, and baseline indicators to identify if the activity displayed is normal for the time period.
SQL Server History - Breakdown
Provides SQL Trace-like granularity without the associated overhead or impact to the SQL workload.
History Workload Overview
Offers built-in business intelligence without the need to build or maintain data cubes. With correlated baseline information to identify normal instance activity and in-context advisory indicators DBAs can find the root cause of performance issues and resolve them with ease.
PA Workload Real-Time
Gain a deeper understanding of normal utilization levels and baseline ranges to improve alerting and diagnose problems caused by resource deviation. Armed with the immediate knowledge that a system is, or is not, behaving the way it usually does helps prove whether the database is the root cause of a performance issue.