We have two tables with 2.9B and 1.1B rows using clustered column store index. New/changed data is only applied once per week in a published application downtime window.We ALTER INDEX ... REBUILD on each table to move changes from the deltastores to the actual compressed index. The REBUILD takes 90 minutes and fits well inside our downtime window. However, a dba (who's not too familiar with columnstores) is insisting on an UPDATE STATISTICS WITH SAMPLE 30 PERCENT, [b]ALL[/b] in this window also. It takes 6+ hours, spills into our normal uptime, and affects application performance.I don't think UPDATE STATS ... [b]ALL[/b] is necessary. UPDATE STATS ... [b]INDEX[/b] runs instantaneously after the REBUILD and proves that the index stats are up-to-date. Also, I think a clustered columnstore index implicitly has column stats and a manual update is redundant. Lastly, I suspect UPDATE STATS doesn't handle clustered columnstore tables well.Any opinions on this? Any articles I can reference so we can decide what to do?
↧