Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI Enhancement: Change default sort order of Execution Stats bar chart #1010

Closed
chadbaldwin opened this issue Sep 17, 2024 · 2 comments
Closed
Labels
Completed DEV work completed. To be included in next release if issue is still open.

Comments

@chadbaldwin
Copy link
Contributor

chadbaldwin commented Sep 17, 2024

This is regarding the bar charts visible on the "Performance" tab along with the itemized detail pop-up.

For the "Execution Stats" bar chart, I think it would be helpful if the sections of the bars were sorted so that the largest sections were on the bottom.

As an example, the "Waits" bar chart graph is already set up this way. But it seems the "Execution Stats" bar chart graph is instead sorted alphabetically, which can make it somewhat difficult to follow.

The only reason I thought of this is because I just recently started using the DBADashReports, and when looking at the Procedure Stats report, it too is sorted by percentage rather than alphabetically and it is easier to see what's going on.

DBADashGUI - Performance - Execution Stats:
image

DBADashReports - Procedure Stats:
image

@DavidWiseman
Copy link
Collaborator

Thanks for the suggestion - makes sense.

Note: The SSRS reports are no longer being developed/tested. They might provide a starting point to build on though if you want some SSRS reports.

@DavidWiseman DavidWiseman added the Completed DEV work completed. To be included in next release if issue is still open. label Sep 27, 2024
@DavidWiseman
Copy link
Collaborator

Included in 3.11 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Completed DEV work completed. To be included in next release if issue is still open.
Projects
None yet
Development

No branches or pull requests

2 participants