Assume that you have partitioned tables in Microsoft SQL Server. When you use CREATE INDEX with new Cardinality Estimator (CE) on the partitioned table, you notice that CREATE INDEX command reads huge rowswhich are multiple times than the total table row count with more CPU andmemory resource cost.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
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: