Open for Voting

Group individual statements/batches in stored procedures

It is nice to report on the execution characteristics of all the statements/batches in a stored procedure.  The individual hashes have to be selected.  We make this a little easier by our naming convention.  The first part of the name identifies the procedure and the last part contains the statement begin and end positions.  DPA should be able to identify all the statements that are included in a stored procedure and present that as an option to include in SQL reports.

Parents
  • I echo the comment by ericp.  Reporting at statement level is great but it doesn't allow you to track the performance of a stored procedure over time. When changes are made to the application/database it would be good to answer questions like what SPs are running slower/more frequently/consuming more CPU/IO etc.  We've had to supplement DPA with our own monitoring using Extended events to be able to answer these types of questions - it would be great if DPA did it all though.

Comment
  • I echo the comment by ericp.  Reporting at statement level is great but it doesn't allow you to track the performance of a stored procedure over time. When changes are made to the application/database it would be good to answer questions like what SPs are running slower/more frequently/consuming more CPU/IO etc.  We've had to supplement DPA with our own monitoring using Extended events to be able to answer these types of questions - it would be great if DPA did it all though.

Children
No Data