If you are using clustered columnstore indexes on Azure SQL databases you run the risk of not being able to access your data when you change your pricing tier.
To demonstrate, I’ll create a basic table and add a Clustered columnstore index.
We’ll insert 2 rows and view the data.
Let’s verify the current pricing tier.
Cool, we’ll change the database to a S2 to save some money.
The boss wants to view some data from that table we created earlier.
Now you know something to watch out for with CCIs.
Leave a Reply