10 thoughts on “SQL Server Quickie #40 – ColumnStore Indexes”

1. 

   Vimal

   10/06/2016 at 10:16 AM

   Nice Quickie Sir 🙂

   I have a question which is not related to this but hope you will help me out.

   What is xp_userlock does and its running so frequently on one of my SQL server 2008R2.

   Reply
2. 

   Klaus Aschenbrenner

   10/06/2016 at 11:03 AM

   Hello Vimal,

   You can find here more information about it: http://lmgtfy.com/?q=xp_userlock 😉

   -Klaus

   Reply
   1. 

      Vimal

      10/06/2016 at 11:27 AM

      Thank You so much for your quick response. 🙂 I already did google but not able to relate it with my scenario. I am getting blocking on my server because of this 🙁

      Reply
3. 

   Andrew Murray

   10/17/2016 at 9:50 PM

   Thanks Klaue.

   Nice and simple presentation and good to know what these different indexes can do. Is there any downside to these sorts of indexes or do they perhaps use more data space ?

   Reply
   1. 

      Klaus Aschenbrenner

      10/20/2016 at 12:06 PM

      Hello Andrew,

      Thanks for your comment.
      There are some performance implications that you have to verify, but normally the ColumnStore Index should give you a great performance in reporting workloads.

      -Klaus

      Reply
4. 

   Qaiser's

   10/24/2016 at 11:10 AM

   Can we Create normal clistered index along with column store clustered index?

   Reply
   1. 

      Klaus Aschenbrenner

      10/24/2016 at 12:53 PM

      No, because there can be only 1 Clustered Index per table.

      Reply
5. 

   Tomasz

   11/07/2016 at 7:08 PM

   Hi Klaus,

   I’me testing the clustered columnstore index right now.
   I’m using the SSDT from VisualStudio 2013.5 for the development.

   When I tried to add a columnstore index:

   CREATE CLUSTERED COLUMNSTORE INDEX ccsidx_yyy ON [dbo].[yyy];
   GO

   I get an error message that:

   Filegroup [XXX] cannot be specified on Table: [dbo].[yyy] when there is the clustered Column Store Index.

   Whats stange that when I ran this command from SSMS the clustered columnstore index has been added to the dbo.yyy table which is using FileGroup.

   Is there any way to solve this issue without moving a table do a different FileGroup (PRIMARY) or to place clustered columnstore index on the whold FileGroup (I’ve found such proposition as well) ?

   Tomasz

   Reply
6. 

   PC Software Download

   12/03/2016 at 6:39 AM

   Nice and simple presentation and good to know what these different indexes can do. Is there any downside to these sorts of indexes or do they perhaps use more data space ? Can we Create normal clistered index along with column store clustered index?

   Reply
   1. 

      Klaus Aschenbrenner

      12/05/2016 at 2:18 PM

      Hello,

      Thanks for your comment.
      No, they use less space because of the applied compression algorithms.
      A traditional Clustered Index doesn’t really make sense.

      Thanks,

      -Klauss

      Reply