Re-teaming is Good: Here’s Why
Note: This post is based on an editorial I originally published over at SQL Server Central Years ago, I worked on a fabulous team of eight database administrators We...
2020-03-13
13 reads
Altering an indexed view in SQL Server drops all indexes
I learned an interesting thing about ALTER VIEW behavior in SQL Server when applied to indexed views. This is covered in the product documentation, but it’s not something I...
2020-03-02
60 reads
Come work with me! Be a Sales Engineer for Redgate
Redgate is growing, and we have some fresh, new open positions around the world which would be a great fit for SQL Server developers or DBAs who would like...
2020-02-21
8 reads
I can do better; we can do better; let’s do better
In the past week or so, the Microsoft Data Platform community has begun having a discussion about inclusivity, both on Twitter and across community blog posts. This conversation began...
2020-02-13
7 reads
Protect Your Prod Databases in Azure DevOps / TFS: Three Control Points
When implementing any kind of automation for database deployments, it’s important to implement safeguards for your production environment. This is needed even in the best conditions when team members...
2020-02-05
14 reads
High Availability options for SQL Server 2008 in an Azure VM – a #sqlhelp story
I asked a question on Twitter yesterday: And check out the magic of the sqlhelp hash tag, I got loads of answers! So many that I’m actually selecting a...
2020-02-01
10 reads
Do It Live! A First Look at Redgate’s Hybrid Model for SQL Source Control and SQL Change Automation (video)
In this 70 minute livestream recording, I kick the tires of a fresh new Azure DevOps demo environment showing Redgate’s Hybrid Model for SQL Source Control and SQL Change...
2020-01-25
6 reads
Controlling who commits code to a given database schema in Git with Azure DevOps
One of most the fun things about working as an Advocate at Redgate is getting to help clients determine their preferred workflow for database DevOps. Teams often have unique...
2020-01-18
13 reads
Re-Inventing Humanity
Wishing you all a very happy, prosperous and peaceful new year 2020! May new year make us Human who cares for all the living being and for our mother...
2020-01-11
21 reads
Re-Inventing Humanity
Wishing you all a very happy, prosperous and peaceful new year 2020! May new year make us Human who cares for all the living being and for our mother...
2020-01-11
5 reads
Blogs
Azure SQL Managed Instance: Boost Performance with Read-Scale Out
By Arun Sirpal
The Business Critical tier of Azure SQL Managed Instance offers the read-scale out feature...
Copying an Azure SQL database between two Azure SQL Instances in two different subscriptions.
I recently had to copy an Azure SQL database (SQL db) from one subscription...
A field note: AI Ambition vs. Operational Reality in 2025
Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
SQL Server Columnstore Index Fragmentation
Comments posted to this topic are about the item SQL Server Columnstore Index Fragmentation
do i lose "what this object depends on" etc when moving sprocs to etl server
Hi i was surprised to see the approach my coworkers used to sunset talend...
Question of the Day
SQL Server Columnstore Index Fragmentation
The columnstore index is absolutely different than the traditional rowstore b-tree index. Because of this, it doesn't suffer from the same kind of fragmentation across pages as the b-tree index. Yet, it does suffer from a type of fragmentation brought about by an excess of deleted rows in a rowgroup and a lack of compression of storage because more things are in the delta store. While b-tree indexes use dm_db_index_physical_stats to show fragmentation, which system tables or DMVs can be used in SQL Server (prior to SQL Server 2025) to determine columnstore fragmentation?
See possible answers