Columnstore index question for the pro's out there.

  • Hey there,

    I'm afraid this is not about data warehousing, but is about columnstore indexes and thought this would be the best place to ask it.

    Lets say I have this huge table, million rows, right now its a bog standard table in a OLTP database and its a subscriber in a Transaction Replication set up.

    Ideally, I want to partition the table up, and put columnstore indexes on it. I'm using SQL 2012 SP2, I realize that columnstore indexes will make the table read only.

    I heard that there is a way of writing to the table so other way, then having the data moved across into the relevant partition, but how can this be done without having to drop the columnstore index? Could someone just outline the method so I have somewhere to start?

    Before I get to that, before partitioning the table and adding the columnstore index, what happens to all the existing indexes on the table? Do these need to be removed?

    Sorry for the newbie Q's, but I'm finding this area really interesting, but only just starting out in it.

    Thanks in advance, I look forward to your wise teachings and sage council!

    Regards,

    D.

  • I'm not an expert on this by any means, but IIRC, you have to create an identical table minus the columnstore index and use partition switching to 'switch in' the data to the table that has the columnstore index defined on it. The following link may help:

    http://social.technet.microsoft.com/wiki/contents/articles/5069.add-data-to-a-table-with-a-columnstore-index-using-partition-switching.aspx

    Regards

    Lempster

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply