Performance Analysis for SQL Server, and Performance Analysis for Oracle, have been long-standing tools in the our portfolio (The following article only applies to SQL Server and Oracle. Performance Investigator for DB2 has not yet been developed). When each product was initially released in early 2000, through much this millennium, Performance Analysis provided unmatched depth of data, as well as the broadest feature set in the industry when it came to analyzing and diagnosing issues related to query performance. Customers raved about Performance Analysis’s feature set, and how it helped them solve complex problems, however the product was not without its faults. Over the years, customer’s environments grew, primarily in the number of database instances each DBA was tasked with managing, but also in the criticality and complexity of their infrastructures. While Performance Analysis continued to provide tremendous value, it became clear that the products legacy architecture was not keeping up with customer demands, so we set out on a project to revolutionize how customers diagnose and analyze query performance problems. The requirement was to maintain the robust feature set that customers have come to expect from Performance Analysis, but build this new solution on a simpler and more scalable architecture, which provides a more modern, web-based user interface. The result of this project, was Performance Investigator (for SQL Server and Oracle). The following post, as well as two others to follow, will cover the differences between the Performance Analysis and Performance Investigator architectures, the new and enhanced features provided by Performance Investigator, as well as the upgrade process for moving from Performance Analysis to Performance Investigator.
Performance Analysis vs. Performance Investigator Architecture
As mentioned above, our primary goal in the transition from Performance Analysis to Performance Investigator was to make the Performance Investigator architecture far simpler, more scalable, and better integrated into a customers existing monitoring solution. The following changes to the Performance Investigator architecture have accomplished this:
Performance Investigator Architecture:
With the above goals in mind, I now present to you the architecture of Performance Investigator. A diagram is also presented below.
Performance Investigator relies on three primary components. Two components are specific to the Foglight architecture, and for those customers running Foglight, are already in place. The third component is specific to Performance Investigator, however fully installed, configured and managed by the Foglight platform.
For more information pertaining to the Performance Investigator Architecture, as well as documentation around the hardware sizing, and prerequisites needed to perform an installation, please consult the Performance Investigator Deployment Guide, which can be found on the product download page for the appropriate solution:
Foglight for SQL Server
Foglight for Oracle