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
147 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
Disclaimer: The following is built with Claude Code. Just need to justify my $100/mo...
By Brian Kelley
I developed these rules a while back, before COVID. I had a period of...
By Steve Jones
Someone asked why I would use TRY_PARSE after I posted a question at SQL...
Comments posted to this topic are about the item The SQL Server MCP Server
Comments posted to this topic are about the item The Hidden Danger of Wildcard...
Comments posted to this topic are about the item A Worse Computer; A Better...
How do I get an MCP server for my SQL Server 2025 database from Microsoft?
See possible answers