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
143 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
A while ago I blogged about a use case where a pipeline fails during...
By HeyMo0sh
Something has shifted quietly in 2026. The developers I know/respect—the ones actually shipping, not...
By Vinay Thakur
Continuing from Day 4 where we learned Encoder, Decoder, and Attention Mechanism, today we...
I have a table I didn't design that has tons of repeating groups in...
Comments posted to this topic are about the item Writing as an Art and...
Comments posted to this topic are about the item String Similarity II
What is the range for the result from the EDIT_DISTANCE_SIMILARITY() function in SQL Server 2025?
See possible answers