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

Feature request: Index history #32

Open
Fiander opened this issue Dec 6, 2021 · 0 comments
Open

Feature request: Index history #32

Fiander opened this issue Dec 6, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Fiander
Copy link

Fiander commented Dec 6, 2021

Would it be possible te build an internal databases with an history of the fragmentation of each index?
that way you could easily see if an index gets a lot of rebuilds.

that would help a lot to determine if an index would be beter of with a lesser fillfactor.
or an index that never needs rebuilding could do with a higher fillfactor.

we have stored procedues in place that check each day if indexes need defragmentation/rebuild, and when an index is rebuild 25 days in a month, the fillfactor is decreased by 5% ( 20 days = 4%, 15 = 3%, 10 days is 2%) . when a index is not rebuild in 30 days, the fillfactor gets 1% higher.

this stabilizes in about a year, and gave us a reducement of IO load of about 15% total.

if you dont like the idea, just remove this request :-) its just a thought.

@sergiisyrovatchenko sergiisyrovatchenko self-assigned this Dec 7, 2021
@sergiisyrovatchenko sergiisyrovatchenko added the enhancement New feature or request label Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants