Database Performance Analyzer (DPA) Quick Demo

Size: px

Start display at page:

Download "Database Performance Analyzer (DPA) Quick Demo"

Blaise Osborne
5 years ago
Views:

Database Performance Analyzer (DPA) Quick Demo http://database.demo.solarwinds.com/ Log in with the username demo and password demo1.

1 Database Performance Analyzer (DPA) Quick Demo Log in with the username demo and password demo1. NOTE: You may encounter the following recommended video, while demoing the product. If you land on this page, just click I ve Seen It to move on.

2. Home Page This is your landing page when you log on to the demo a.

2 1. DPA Overview Database Performance Analyzer is designed to identify and locate bottlenecks throughout your database environment, based on wait times and or events, with the goal of finding bottlenecks and issues within 3-4 clicks of the mouse. 2. Home Page This is your landing page when you log on to the demo a. Dashboard gives you a quick snapshot of any critical issues that might be taking place in all monitored databases instances. 3. Database Trends (SQL) Database Instance > Production > SEBOX1/SE2008R2

3 SQL Statements SQL Statement List a. This graph shows the top SQL Statements in a 30 day rolling window. b. The Bar Graph Each bar represents wait time for a particular day with each colored section representing, in this case, a specific SQL statement. The Statement list on the right shows which SQL statement corresponds to which color. i. You can also hover over any section of the bar to view the details of that statement. c. Analyze Query Drop Down Analyze Query drop down i. Each query present in this graph can be analyzed by DPA for high execution and wait times as well as providing advice to improve query performance. NOTE: If the customer wants to see an analysis, you can select a query and run the analysis on the demo. d. From here, we can quickly drill down into the details to find the root cause of this database s performance issues, with just a few more clicks of the mouse.

4 Click and Drill into one of the red bars for August 23 rd, for details. Click Here e. The Day View This view shows the same information as the trend overview in the previous chart, but here it s broken down into a 24 hour view of the top SQL Statements for August 23 rd only. i. In this view, it s clear that the highest utilization is between 10AM and 6PM. However, we may also want to know if any of this activity is outside normal behavior. We can make that determination, using baselines.

f. The Resources View Click the Resources tab. i. Resources can be tracked to establish a baseline over time, all the way down to an hour by hour analysis if needed.

5 f. The Resources View Click the Resources tab. i. Resources can be tracked to establish a baseline over time, all the way down to an hour by hour analysis if needed. Scroll down to the Memory Paging Rate graph Activity Spike Baseline ii. Here, we can see a dark line representing the baseline activity, and bars showing the actual activity. We can see a spike in activity at about 1PM that is quite a bit outside the normal. iii. From here, we can drill into a specific time if, for example, a complaint was voiced about the database being slow around 1 PM. Click and drill into the red bar for 1PM to view the details. Click Here SQL Statements List of Waits Wait/Response Time NOTE: Main competitors, such as Idera cannot show all three of these metrics in one view!

6 g. The Hour View In this view, the data is broken down by each SQL statement, represented by the bars, over the 1PM to 2PM timeframe. Each colored segment represents a wait type, defined by the list on the right. So now we can see the wait type on each statement, over the hour timeframe. h. Identify the Bottleneck Hover over the Delete_kg statement blue bar i. Here, we can see from the list that our biggest bottleneck in this statement is PAGEIOLATCH_EX represented by the blue bar. ii. When we hover over that bar, we can see that the wait time for PAGEIOLATCH_EX represents 74% of the total wait time or 22:12 minutes of the total 29:53 wait time on this statement. NOTE: The wait time and percentages may vary in this window and not be the same numbers as the screenshot below. i. So, with four clicks of the mouse, we have identified the specific query, wait type and wait time by the query at a specific bottleneck. In other words, we have found the root cause of the database slowness. But, let s take this further and closely examine the bottleneck.

I/O is a very common reason for database slowness, so we re going to take a close look at it. Database Files ii.

7 i. Wait Time and Storage I/O Click the Waits tab Click Storage I/O next to Trends i. Now, we re seeing the wait time and PAGEIOLATCH_EX is still at the top of the list so the next step is to try to determine what is causing the wait. I/O is a very common reason for database slowness, so we re going to take a close look at it. Database Files ii. Here, I can see the wait time per file for Read, Write and Current, depending on which tab I select. Here, we re looking at Read performance. In the first graph, I can see a definite spike in read performance around 1:17PM and lasting until around 1:19 PM for a specific file as shown in the list.

Here we have the details of the bottleneck including suggestions on possible solutions for

8 j. Bottleneck Detail Return to the Trends view > Click on the PAGEIOLATCH_EX wait in the Wait List. i. Here we have the details of the bottleneck including suggestions on possible solutions for the issue. ii. You can also click on the wait in the bar graph, to view the details of the query. Close the description window and click the wait bar to view the SQL query.

9 At this point, the main functionality of DPA has been demo d. Additional features are available in the DPA Supplemental demo document found on Confluence.

Explore metrics in the ExtraHop system to investigate DNS failures

Explore metrics in the ExtraHop system to investigate DNS failures Published: 2018-02-06 The DNS (domain name system) protocol is critical for supporting internet traffic. It often works without issues.