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
By Brian Kelley
There's a great article from MIT Technology Review about resetting on the hype of...
By Steve Jones
etherness – n. the wistful feeling of looking around a gathering of loved ones,...
By Steve Jones
A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...
Comments posted to this topic are about the item The Microsoft SQL Year in...
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Comments posted to this topic are about the item Your Value from a Conference
What does this code return in SQL Server 2025+? (assume the database has an appropriate collation)
SELECT UNISTR('Hello 4E16754C') AS 'A Classic';
A: 
B: 
See possible answers