The SQL view gives a complete performance overview of the selected SQL statement. The chart may be toggled between total time spent, or the individual wait-state breakdown.
The key performance indicators at the top of the screen are there to show top level metrics and alerts.
- DB Time - This is the total amount of time spent executing this SQL statement within the selected period.
- Executions - This is the total number of executions for the SQL statement within the selected period (not always available depending on the database type)
- Average Time - This is the average SQL response time within the selected period (not always available depending on the database type)
- Change History - This shows 2 values: 1) the total number of changes within your environment such as schema changes or database parameter changes within the time range selected and 2) any custom events you have created for things like code releases or infrastructure changes.
Statement performance over time
This shows the DB time and wait states over time for the SQL statement. You can optionally toggle the wait-states on of off with the button in the top right.
- The chart shows where the SQL was executed from. For example which client, user, program and database the SQL was run against. Note this table is not displayed in Beta release 0.1.
- The charts shows a breadkown of the SQL statement time by wait state.
Shows the formatted SQL text.
You can use the icon in the top right to copy the statement to your clipboard.
If the SQL statement had multiple explain plans within the selected period you will see a dropdown where you can toggle between the different plans and see what changed. Note that the the time range when a plan was used represents the earliest and latest times that plan was used. So if a new plan was used for a short period, before reverting to the original, then the plan time ranges overlap.
Explain plans are generated automatically by DBmarlin as a background process. When you have many SQL statements only the top statements will get explained each time it runs.
The plan format for Oracle, PostgreSQL, MySQL, IBM Db2 and CockroachDB is a tree view with master detail like below.
The plan format for SQL Server is similar to what you might see in Microsoft SQL Management Studio. It also includes recommendations such as missing indexes as seen below.
To understand how to interpret an execution plan see the knowledge base section here.
Shows any database changes for the database instance where the SQL ran such as DB parameter changes or schema changes.