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 Brian Kelley
If you are considering any of the ISACA AI certs like the Advanced Artificial...
By ChrisJenkins
Are you currently using Microsoft Fabric or considering migrating to it? If so, there...
By SQLPals
Track SQL Server Configuration Changes Using the Error Log If you...
Comments posted to this topic are about the item We Are Eating Our Own...
Artificial intelligence tools are quickly becoming part of daily business operations, from document analysis...
Comments posted to this topic are about the item Designing SQL Server ETL Pipelines...
In the Database Engine, when a deadlock is detected, what does the detection interval shrink to (in time)?
See possible answers