This is the true story of a 64-core SQL Server brought down by poor assumptions about its data. A clustered index designed for neat, sequential IoT inserts was overwhelmed when the real readings arrived late, out of order, and in bulk. The same risk lurks in any high-write system with unpredictable insert patterns. This article shows what can go wrong and how to avoid it.
2025-11-14
2020-06-10
148 reads
Was the marketing hook 'The Internet of Things' conjured up before the technical definition? Are we being persuaded to spend money on fending off yet another fantasy tsunami of data? Already, we have televisions that listen to, and report, your conversations; so are we facing the Science Fiction future of gadgets that report where you go, who you visit and what medications you take? As Robert Sheldon says; "It's big, almost too big to get your arms around".
2015-04-10
11,037 reads
By James Serra
Most enterprise questions do not live neatly in one place. The numbers may be...
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
Telp/Wa 62 8218200233 PQHX+93W, Jl. RS. Fatmawati Raya No.6 A, RT.1/RW.5, Cipete Sel., Kec....
Telp/Wa 62 8218200203 Gedung Gajah Tebet, Jl. Dr. Saharjo No.Raya 111 Unit N &...
Telp/Wa:62 8218200174 Jl. Tebet Barat IX No.40, RT.6/RW.4, Tebet Bar., Kec. Tebet, Kota Jakarta...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers