Consider the following scenario:

  • You have a partitioned table that contains a nonclustered index in Microsoft SQL Server 2008 R2.

  • You create a clustered index that is based on the first column in the partitioned table.

  • The table uses the partition key as the first column.

  • You create a filter on the partition key.

  • You try to create a filtered statistic for one of the columns.

In this scenario, it takes longer than expected to create the statistic.


  • The query plan that generates a CREATE STATISTICS statement indicates that the query performed a full scan on all the partitions.

  • If you create another nonclustered index, it does not take longer than expected to create the statistics for columns that are not related to the nonclustered indexes.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!