The Performance Divergence Monitor reports daily the performance metrics and SQL statements whose performance diverged from a weekly, monthly, quarterly or annual performance baseline.
View in a 100% web enabled interface server farm performance divergences. A PDF report of performance divergences may also be emailed to management and the DBA team. Sql Power Tools unique usage of 3D visualization from a web browser allows the server farm performance divergences to be viewed in a single 3D picture.
Performance counter divergence:
For the Windows operating system performance counters and SQL Server performance counters, the product reports for every database server in the server farm the servers that had performance counters that exceeded a prior time period’s baseline by a threshold percentage or value.
SQL statement performance divergence:
For the application SQL that 80% of all database performance issues are caused by, the product reports for every server in the database server farm the servers that had SQL statements with performance that exceeded a prior time period’s baseline by a threshold percentage or value. Most database server applications contain 2,000+ unique SQL statements that client applications invoke 50 million+ time a day, the performance divergence of every unique SQL statement for every database server is tracked and reported.
How database server farm performance divergence analysis may be used in production environments:
Open a web browser and view any of the following with 3D visualization:
- Servers prod1 and prod50’s total CPU usage was 6% higher than last week’s CPU usage.
- Servers prod19 and prod250’s disk usage was 15% higher than last month’s disk utilization.
- Servers prod30 and prod8’s average end-user response time was 13% higher than the prior month.
- Servers prod3 and prod7’s average network time for SQL statements was 17% higher than the prior month.
- Servers prod35 and prod80’s database blocking incidents were 12% higher than the prior quarter.
- Servers prod25 and prod70’s deadlock incidents were 14% higher than the prior quarter.
- Servers prod51 and prod100’s SQL table scans yesterday were 25% higher than the prior year.
- Servers prod41 and prod150’s SQL re-compilations yesterday were 20% higher than the prior week.
- Servers prod41 and prod120’s average wait-time for locks were 30% higher than the prior week.
- Server prod71’s SQL Server CPU usage between 2pm and 4 pm was 25% higher than 10 am and 12 pm.
- Compare the capacity and performance of server prod7 to the servers prod44, prod51 and prod88.
- Server prod5 had 8 of its 4,000 unique SQL statements run 18% longer than yesterday. 12 of its SQL statements ran 15% longer than their baseline over the past week.
How divergence analysis may be used in migrating to SQL Server 2008:
To pinpoint the performance divergences between applications previously running on SQL Server 2000 and 2005; and that have been migrated to SQL Server 2008.
How divergence analysis may be used in QA environments:
To pinpoint the performance divergences between this application turnover and last quarter’s turnover.
This product is currently available for Microsoft SQL Server.