Stairway to Snowflake Level 8 - Event Tables
In this next level of the Stairway to Snowflake, we delve into Event Tables. These are used to capture telemetry from your Snowflake database.
2025-07-02
391 reads
Mike McQuillan
A CONCAT Function For The Rest Of Us
SQL Server 2012 introduces a new string concatenation function. This can be recreated in earlier versions of SQL Server.
2012-06-06 (first published: 2012-05-16)
2,161 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