Partitioned Columnstore Index Defaults to Estimated Rowcount 1 with Primary Key - by wBob

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 808388 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/12/2013 1:51:35 PM
Access Restriction Public


Estimated Rowcount for columnstore index scan defaults to 1 with moderately complex data warehouse query against partitioned table with primary key.  Actual rowcount can be millions.  Bad CE can result in Nested Loops and poor performance.
Sign in to post a comment.
Posted by Neugebauer on 7/31/2014 at 5:33 PM
Just tried the attached script on SQL Server 2014 with CU2 and it works fine.
Posted by swasheck on 7/2/2014 at 12:29 PM
Is there an update available that addresses this issue?
Posted by Microsoft on 1/5/2014 at 7:22 PM
Thanks for submitting this feedback. This issue has been resolved. A fix will be available in an upcoming release of SQL Server. We will update you when the fix has been shipped. Thanks for your continued support in impoving SQL Server.
Posted by NigelRivett on 11/13/2013 at 2:08 AM
I was the first to report this bug and it is causing me a lot of grief.
For the moment we are using the forcescan index hint to get around it but the user access is via a view and this means exposing the underlying object.