Prakash Heda

Prakash Heda works as Sr. Database Administrator at Advent Software. His expertise includes Performance Tuning/Troubleshooting, high availability, SAN configuration and windows administration. He has 13+ years of experience managing enterprise-wide data needs in both high volume transactional and data warehouse environments. Prakash holds certifications for MCDBA and MCITP. His background includes administration & development using VB/ASP/SSIS using SQL Server 2000, 2005 and 2008/R2 and SQL server 2012. He is an active member of PASS, SQL Saturday. He’s a frequent presenter at user groups, SQL Saturdays, and other community events. He is also an avid tweeter, blogger and runner.
  • Interests: Computers, Chess, Reading

All authors

All authors

Blogs

A field note: AI Ambition vs. Operational Reality in 2025

By

Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...

Redefining Tech Leadership in the Age of Microsoft AI

By

AI is no longer a niche capability – it is a leadership catalyst. As...

Sample Data with GenAI in Seconds

By

A friend was asking for help with some data analysis. This was in PowerBI,...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

SQL Server Columnstore Index Fragmentation

By Grant Fritchey

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

By stan

Hi i was surprised to see the approach my coworkers used to sunset talend...

Visit the forum

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