GSquared (8/6/2012)

---

Complexities like these are one of the myriad of reasons I consider such systems horribly flawed in the vast majority of cases. They make documentation more difficult. ...

Excellent post, and one that really struck a chord with me.

I, too, take delight in being wrong, for pretty much the reasons that Hakim outlined. But there is another...

Understood. Mulling it...

Thanks Gail, great article.

I thought I had a decent grasp of logging issues, but I must admit that I had a light-bulb moment when you described the Eager Write mechanism!

David Walker-278941 (7/27/2011)

---

Ewald Cress (7/27/2011)

---

Back on the secondary subject of larger pages, I guess the obvious argument against them would be buffer cache wastage. If you have hundreds of often-used...

Steve Jones - SSC Editor (7/27/2011)

---

Ewald Cress (7/27/2011)[hr

I wonder how committed Microsoft is to the 8K page size. A quick look in BOL shows that it is "officially documented", although...

Eric M Russell (7/27/2011)

---

In addition to Microsoft retrofitting the storage engine itself, MSDN and the entire SQL Server community would have to retrofit all of our DMV and system table...

Back on the secondary subject of larger pages, I guess the obvious argument against them would be buffer cache wastage. If you have hundreds of often-used lookup/dimension tables with only...

Larger pages sound kind of inevitable at *some* point in the future, and I can't imagine they'd change the basic concepts we deal with.

However, ROWIDs would be a different...

I'm trying to get some clarification as to where that row estimate comes from. It's not from statistics, there's no auto stats events fired and no stats visible in TempDB...

Matt's comment notwithstanding, I still think Jeff has a point. If he were preaching to the converted, it would be a tired old point, but far too many developers still...