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
142 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 Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forgive me for the title. Mentally I’m 12. When I started my current day...
By Steve Jones
One of the things a customer asked recently about Redgate Data Modeler was how...
Comments posted to this topic are about the item Expanding into Print
Comments posted to this topic are about the item Downtime Caused by the Postgres...
Comments posted to this topic are about the item The String Distance I
In SQL Server 2025, what is returned by this code:
SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled. See possible answers