Home Dashboard Directory Help
Search

CREATE COLUMNSTORE INDEX should support adding all columns by xor88


Status: 

Active


2
0
Sign in
to vote
Type: Suggestion
ID: 766693
Opened: 10/9/2012 4:06:11 AM
Access Restriction: Public
0
Workaround(s)
view

Description

The CREATE COLUMNSTORE INDEX syntax should be extended to support adding all eligible columns (as opposed to specifying all of them individually).

Adding all eligible columns is the current official recommendation anyway. In many cases this is just the right thing to do.

It could look like this:

    CREATE NONCLUSTERED COLUMNSTORE INDEX CS_Table ON Table (*)

As an alternative to the star the keyword ALL could be used.
Details
Sign in to post a comment.
Posted by Microsoft on 4/29/2013 at 2:31 PM
Hello,

Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing this bug is because the scenario reported in the bug are not common enough and due to the risk of implementing a fix it unfortunately does not meet the bar for the current version of the product.

If you have more supporting information and details or feel strongly that we should reconsider, please do resubmit this item for review.

Thanks again for reporting the product issue and continued support in improving our product.
Gus Apostol, SQL Server Program Manager
Posted by Wim SQL Server on 10/11/2012 at 3:56 AM
Maybe what you are saying is to allow the choose how you want a table to be stored: row based or column based..
If a table would primarily be used by selecting column selective queries 'SELECT Col1,COL2 FROm Table' this would be better to store the table as a columnstore table.

Maybe even we should allow a 'columnstore filtered index', I'll make a separate topic for this.
This should really be looked into more in detail..
Sign in to post a workaround.