After seeing multiple people switch from STRING_SPLIT() to OPENJSON() to deal with multiple parameters, I decided to explore whether that is a change in the wrong direction.

I talk about NULLs in SQL Server, the logical issues with avoiding them, and potential performance impacts.

Updated this stored procedure I wrote a decade ago to search for a string in procedure bodies, object names, job steps, and more…

I talk a bit about bit columns: names with negative context, allowing NULLs, and using cryptic BITWISE operators instead of readable, self-documenting expressions.

For this month's T-SQL Tuesday, I talk about the scripts I use to keep a local system with all kinds of oddball metadata scenarios.

In this tip, I use specific examples to counter assumptions that data types are always case insensitive.