Enhancement Request: Support page-count filtering or prioritization for statistics updates in IndexOptimize

[sm8680]

Hi Ola,

Per our recent email discussion, I am creating this issue to capture the idea for future consideration.

'MinNumberOfPages' and 'MaxNumberOfPages' currently apply to index maintenance only. Statistics updates are performed regardless of index/table size.

Would you consider adding an option for statistics maintenance to support page-count filtering or prioritization?

For example, possible parameters could be:
@StatisticsMinNumberOfPages
@StatisticsMaxNumberOfPages

or an option to let statistics maintenance honor the existing page-count settings:
@StatisticsUsePageCount = 'Y'

Use Case

In VLDB environments, statistics maintenance can also be expensive. It would be helpful to prioritize or scope statistics updates by object size, similar to how index maintenance can be scoped today.

This would allow maintenance jobs to handle large, medium, and small objects separately, while also giving DBAs better control over statistics maintenance during limited maintenance windows.

I understand this may not be something that can be implemented soon, but I wanted to capture the idea as requested.

Thanks,
Steven