A few weeks ago I was talking with a friend about upcoming plans. Without thinking, I said:
“Oh, and I’m going to go to Cleveland to talk about Isolation Levels. And partitioning. In February.”
This post is about two things:
You should confirm you are running with the correct page verification settings on your SQL Server databases. It’s very important, and I’ll show you why.
My scripts to demo the importance of page verification settings are part of my entry to win free registration to the SQLSkills Master Immersion Event on Internals and Performance in February. Read more about the training here.
This Post Tells You How To Corrupt a SQL Server Database with a Hex Editor in Gruesome Detail
And that’s all this post tells you. Not how to fix anything, just how to break it.
Optimizing queries is the most fun when you don’t need to add indexes. There’s nothing quite so nice as finding a way to make reading data faster, without slowing down writes or creating new data structures that need to be maintained.
Recently I read Paul Randal’s ( blog | twitter ) post, “So you want to blog about SQL Server?” and it got me to thinking.
This month’s #tsql2sDay is hosted by Jen McCown ( blog | twitter ) and Jen’s question is “What techie resolutions have you been pondering, and why?”
With every new year I think a little bit about time and dates. This posts looks a little more at that in TSQL.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.