Road trip time! I’m recovering from jet lag after flying over to Iceland, so I went through your top-voted questions from https://pollgab.com/room/brento.
Here’s what we covered:
- 00:00 Start
- 00:55 Shehroz Sabzwari: What are your pros / cons for running on-prem SQL Server in a VM versus bare metal?
- 02:04 adba: what are your recommendations for windows performance plan for sql server running on a VM. My private cloud vendor says it is not required to be set to high performance.
- 03:25 Holy: Can’t you agree that all RDBMS databases are approaching their limits, just as ISAM databases did in the 1980s and 1990s?
- 05:47 sandimschuh: Hi Brent, is it always safe to change the database setting from Read Committed to RCSI? What kind of queries or query patterns will be negatively affected by this change?
- 07:04 Mike Conrad: Hi Brent, My team uses system versioned tables a lot. Our ORM, EFcore, sometimes will write updates that don’t change any data, but this does generate a new HISTORY table row, bloating our audit trail. Are instead of triggers a viable way to prevent this?
3 Comments. Leave new
I come to Brent not just for the knowledge – but how he explains it. How to “play database” or demonstrating page splits using the names of those in the first row (no pun intended). Walking through the simplified steps the RDBMS takes is an eye opener.
Aww, thanks sir!
I don’t think Holy understands what VSAM, RDBMS or NoSQL do/did.
NoSQL re-introduces some of the problems VSAM had that led to the rise of the modern RDBMS to achieve better availability and aggregate read performance at the expense of integrity, consistency and write concurrency. The more heavily sharded a NoSQL database is, the more it is going to sacrifice to provide greater read performance and availability.
Normalization, atomicity, consistency, integrity and durability are concepts that will never be obsolete in the systems that require them. Maybe one day NoSQL databases will implement ACID compliance, (architecturally for how they work, I doubt it) but normalizing NoSQL would be like proclaiming that water is dry.
There is a pretty interesting youtube video going over some of the growing pains Discord had in their service (back ended by NoSQL) and how they dealt with some of their problems, but also what specific issues their architecture resolved for them.