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.
In A Previous Installment… our heroine (that’s me) rediscovered CTEs, specifically in the recursive style. That was in my post “Filling in Data Potholes with Recursive CTEs.”
The MorningNews asked the following question recently:
Who you would recognize in your 2010 liner notes?
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.