Does IndexOptimize doesn't really consider all indexes? #789
Replies: 1 comment
-
I've seen that the "problem" was the @PageCountLevel, as it's default is 1000. Most of my indexes page_count was < 1000. So there's no problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my database, I got over 300 indexes that have > 30% fragmentation, checking running the following script:
Then I run the the IndexOptimize in the simplest way to fix the fragmentation of all indexes:
First time I've executed it, the message shows some indexes being repaired, but after it finishes I run the first script again and it still shows over 300 indexes with >30% fragmentation. So, does the IndexOptimize script is ignoring most of the indexes (at least in my case)?
Note: all the indexes are nonclustered or clustered. None of them are ColumnStore (I've found some discussions talking about a possible bug over this type of index).
Beta Was this translation helpful? Give feedback.
All reactions