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 :)
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 :)