Fillfactor indexes #204
Open
Fillfactor indexes #204
Conversation
This file contains 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
|
|
| IF @ptochecks = 1 | ||
| BEGIN | ||
| RAISERROR (N' |-Starting Indexes with fill factor = 100 pct', 10, 1) WITH NOWAIT | ||
| IF (SELECT COUNT(*) |
There was a problem hiding this comment.
What about?
IF EXISTS (SELECT TOP 1 1
There was a problem hiding this comment.
Good point. I just reused the code that is currently in the stored procedure. Yes in some situations it could exists big differences in performance but in this case is just metadata information and not thousands of rows so differences in performance are not expected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It was included the return of fragmented indexes that have fill factor with 100%. This situation could cause impact on indexes with high volume of updates that could generate page splits.