microsoft
Columnstore fragmentation can be > 100, but @rebuildThreshold_cs is capped at 100
The results of the columnstore fragmentation calculation can be greater than 100 (lines 1247-1261), but the value passed into @rebuildThreshold_cs is capped at 100 (lines 492-493). This makes it impossible to setup a job to only reorganize columnstore indexes.
There's no logical point is using a percent above 100. Capped the max columnstore frag calculation to 100 in v1.6.6.8. If I'm not following your intent, please explain.
The fragmentation percentage getting by calculated the index maintenance job and stored in the is sometimes above 100. If the the threshold for a rebuild can never be greater than 100, then any columnstore index that reports fragmentation greater than 100 will be force a rebuild. In some cases, we don't want to do a rebuild of those columstore indexes, but a reorg is ok. The scripts don't give a way to handle this scenario.
The threshold should either allow values up to the max fragmentation that can be calculated, or the calculation should be changed to report fragmentation as a percentage.
-Tim Landrum
On Wed, Jun 19, 2019, 23:10 Pedro Lopes [email protected] wrote:
There's no logical point is using a percent above 100. Capped the max columnstore frag calculation to 100 in v1.6.6.8. If I'm not following your intent, please explain.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/microsoft/tigertoolbox/issues/115?email_source=notifications&email_token=ALOC5QS2ZRWMGCM7IKXYMW3P3LYK7A5CNFSM4G2A3L6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYD34LI#issuecomment-503823917, or mute the thread https://github.com/notifications/unsubscribe-auth/ALOC5QSMSOCR4H45WIT4UALP3LYK7ANCNFSM4G2A3L6A .