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.
This is a little change I whipped up for a feature I call "smart stats". This is based on an article here: https://www.i-programmer.info/programming/database/5170-improve-sql-performance-an-intelligent-update-statistics-utility.html
I have had good luck avoiding bad plans on occasion using these sample sizes...
This implementation is not ideal, but rather the least intrusive way I could do it. Basically passing -1 for the @StatisticsSample parameter will use this new algorithm. Sharing in case you like it and are interested in including some version of the logic :)