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
By Steve Jones
Thanks to everyone for attending my session on running a Local LLM. If you...
By Steve Jones
I do believe that Redgate has been very customer focused since it’s inception. I’ve...
By gbargsley
It's 2 AM. Your phone is going off. Users can't connect to the application,...
Hi everyone I am getting below warning when I run SSIS: Warning: 0x80049304 at...
Comments posted to this topic are about the item Let's Talk Community Events!
Hi as shown below a replication target requires a primary key. if we want...
By default, how often is the SQL Server Database Engine checking for deadlocks?
See possible answers