2016-04-05
2 reads
2016-04-05
2 reads
2016-04-05
1 reads
2015-10-19
2 reads
2015-10-19
2 reads
2015-10-19
1 reads
Detecting worst performing queries executed in a particular duration and how many times it got executed and fine tuning them is a single most efficient technique to fix unexpected...
2015-10-19
2 reads
Detecting worst performing queries executed in a particular duration and how many times it got executed and fine tuning them...
2015-10-19
825 reads
on 10th oct 01.30 pm pst, i will be speaking on “detect worst performing sql queries during peak hour” @ sqlsaturday,...
2015-10-05
772 reads
2015-10-05
2 reads
2015-10-05
1 reads
I recently had to copy an Azure SQL database (SQL db) from one subscription...
Ivan Jelić, Group CEO at Joyful Craftsmen, reflects on what separates AI success from...
By Chris Yates
AI is no longer a niche capability – it is a leadership catalyst. As...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item SQL Server Columnstore Index Fragmentation
Hi i was surprised to see the approach my coworkers used to sunset talend...
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