For this T-SQL Tuesday, I talk about a few of the difference makers in my career.
Category: T-SQL Tuesday
For this T-SQL Tuesday, I describe a few of my experiences from the 2000s, from both sides of interviews.
For T-SQL Tuesday #92, I show one trick I use to prevent errant DML from running in production.
I recount the way I implemented database changes in a distributed SQL Server system a decade ago.
For T-SQL Tuesday #87, I talk about two shiny new toys in SQL Server: STRING_SPLIT() and STRING_AGG().
For T-SQL Tuesday #86, I highlight a few of my favorite bugs and feature requests on Connect (RIP).
For both T-SQL Tuesday and #BackToBasics, I provide information about SQL Server backups, and why your restores can be just as important.
I submit a wish list item for the 80th T-SQL Tuesday: CREATE OR REPLACE, a cleaner way to deploy objects without losing permissions.
For this T-SQL Tuesday, I talk about a feature long missing from SQL Server: The ability for Developer Edition to act like Standard.
For T-SQL Tuesday #78, I take a look at whether RID Lookups are faster than Key Lookups, with a small battery of fairly simple duration tests.
For this T-SQL Tuesday, I treat some of the most memorable data modeling sins from over the years.
For this T-SQL Tuesday, I talk about a few of the limitations of Always Encrypted.
I look at the tempting All Features With Defaults installation choice for this T-SQL Tuesday.
For T-SQL Tuesday #67, I describe a new way to track backup and restore operations using Extended Events in SQL Server 2016.
For T-SQL Tuesday, I discuss undocumented trace flags that provide additional diagnostics to troubleshoot slow backup or restore operations.
For T-SQL Tuesday< #65, I give a little detail on something I learned this week about altering a column from NOT NULL to NULL.
I follow up on a question from a triggers presentation at SQLBits, addressing the impact of trigger overhead for T-SQL Tuesday.
For T-SQL Tuesday #58, I discuss a few of the reasons people give out the sa password, and what you should do in those cases instead.
I use a T-SQL Tuesday theme to demonstrate a use case for the SQL_VARIANT data type that you may not have considered: Conditional ORDER BY.
This month's T-SQL Tuesday is about assumptions in SQL Server.
Last week I attended the PASS Summit in Seattle. I blogged from both keynotes (Keynote #1 and Keynote #2), as well as the WIT Luncheon – which SQL Sentry sponsored. I had a fantastic...