Conversation
…o shows all indices for the given table. This serves as a companion piece to the Table Information page which our customers rely on heavily. This page will help with two main scenarios: Insights into per-index storage usage - our customers have very limited insights into the storage size, with the current Table Information only showing a SUM of all indices, they cannot know which index is taking most of the space. Further, in scenarios where the index was created by DAMS, they cannot even know about it, potentially making the space used suddenly go up. Insights into index usage - Some indices are likely added and underused, which then just has a cost on alterations and uses unnecessary database storage. Add usage insights in the form of number of operations and when the last operation happened against the index.
duichwer
reviewed
Feb 12, 2026
NKarolak
suggested changes
Feb 13, 2026
Contributor
NKarolak
left a comment
NKarolak
left a comment
There was a problem hiding this comment.
I was asked to nitpick, so I did ;-)
Please apply to the other page object as well.
duichwer
reviewed
Feb 13, 2026
NKarolak
suggested changes
Feb 13, 2026
github-actions
Bot
added
the
Build: Automation
aholstrup1
previously approved these changes
Feb 14, 2026
added 2 commits
February 15, 2026 11:51
…thub.com/microsoft/BCApps into features/621484/TableInformationOnBCApps
NKarolak
reviewed
Feb 16, 2026
BardurKnudsen
previously approved these changes
Feb 16, 2026
mazhelez
approved these changes
Feb 16, 2026
BardurKnudsen
approved these changes
Feb 16, 2026
darjoo
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This serves as a companion piece to the Table Information page which our customers rely on heavily.
This page will help with two main scenarios:
Insights into per-index storage usage - our customers have very limited insights into the storage size, with the current Table Information only showing a SUM of all indices, they cannot know which index is taking most of the space. Further, in scenarios where the index was created by DAMS, they cannot even know about it, potentially making the space used suddenly go up.
Insights into index usage - Some indices are likely added and underused, which then just has a cost on alterations and uses unnecessary database storage. Add usage insights in the form of number of operations and when the last operation happened against the index.
Work Item(s)
Fixes AB#621484