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
139 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're looking for particular "Black Friday" deals, here is what I've seen advertised...
By SQLPals
Dry-run xp_delete_file Before Actually Deleting Files? xp_delete_file doesn’t really have a...
By Brian Kelley
In the United States, today is Thanksgiving. The intent behind the holiday is to...
Comments posted to this topic are about the item Don't Let Corner Cases Drive...
Comments posted to this topic are about the item A New Operator
Comments posted to this topic are about the item Troubleshooting Common SQL Server Errors:...
In SQL Server 2025, what does this code return?
SELECT '1' || '0'See possible answers