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
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...
By Steve Jones
For a number of years, we’ve produced the State of the Database Landscape report,...
Hi all, I've just had to roll back my SSMS 22 version from 22.3.0,...
Hi! I've been banging my head against the wall for 2 days now trying...
Comments posted to this topic are about the item The Power of Data and...
In SQL Server 2025, there is a new function that returns the current date without the time. What is it?
See possible answers