tl;dr The title says it all. Prologue One of the keys to my personal learning is that, very early in my database career, I taught myself how to make lot’s of rows of Random Constrained Data in a comparatively short time. With the help of a few good folks over time, the method has been […]
2026-06-24 (first published: 2023-09-18)
4,119 reads
One of the more challenging technical details of columnstore indexes that regularly gets attention is the need for data to be ordered to allow for segment elimination. In a non-clustered columnstore index, data order is automatically applied based on the order of the underlying rowstore data. In a clustered columnstore index, though, data order is not enforced by any SQL Server process. This leaves managing data order to us, which may or may not be an easy task.
2023-08-09
By Steve Jones
I wrote about learning today for the editorial: I Can’t Make You Learn. I...
By ReviewMyDB
Fabric has CI/CD built in, but if you've tried to use it for database...
By Steve Jones
attriage – n. the state of having lost all control over how you feel...
WA:08218154393 Jl. Jend. Sudirman No.49-51, Terban, Kec. Gondokusuman, Kota Yogyakarta, Daerah Istimewa Yogyakarta 55223
WA:08218154393 Jl. Kisamaun No.57, RT.001/RW.006, Sukasari, Kec. Tangerang, Kota Tangerang, Banten 15118
Comments posted to this topic are about the item Forward Deployed Engineers
I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?
See possible answers