2021-12-06
384 reads
Database Snapshots
2021-04-26
497 reads
2011-07-15
2,283 reads
2010-11-09
2,476 reads
2010-07-29
2,637 reads
Database Snapshot and Rollback Transactions
A Rolled back transaction will increase the snapshot sparse file usage. New author Subash brings us an examination of how those database snapshots actually work.
2010-01-07
5,170 reads
2009-08-27
2,865 reads
2009-01-16
3,122 reads
2009-01-13
2,779 reads
2008-12-30
2,815 reads
Blogs
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...
Redefining Tech Leadership in the Age of Microsoft AI
By Chris Yates
AI is no longer a niche capability – it is a leadership catalyst. As...
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