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
150 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
Can you use your GPUs when running a local model under Ollama? You can,...
By Brian Kelley
The concern that a particular technology is going to destroy the world seems to...
The STIG is detailed, which is a good thing, but I found myself wanting...
Telp/Wa 62 8218200233 Gama Tower Lt. Dasar Unit B, Jl. H. R. Rasuna Said...
Comments posted to this topic are about the item RegEx Functions III
Comments posted to this topic are about the item Optimized Locking in SQL Server...
If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.
See possible answers