The Basics of Good T-SQL Coding Style

TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.

@@rowcount and the OUTPUT clause

OUTPUT clause with an update

Use T-SQL to Find Folders Using the Most Disk Space

Your SQL Server drives are running out of disk space and you want a way to quickly tell which sub-directories are taking the most space - here's how to do it with T-SQL.

The OUTPUT Clause for the MERGE Statements

In this article, I will provide a set of examples to showcase the use of OUTPUT clause within the MERGE statement and how to capture the OUTPUT clause results into an archive table.

The OUTPUT Clause for UPDATE Statements

In this article, I will provide a set of examples to showcase the use of OUTPUT clause in capturing the results of the updated rows into a table variable for the UPDATE statements.

Masking short domains

The OUTPUT Clause for INSERT and DELETE Statements

In this article, I will provide a set of examples to show case the use of OUTPUT clause for INSERT and DELETE statements.

Some of my greatest mistakes

You are never too experienced to make mistakes. An occasional dose of humble pie serves as a reminder to up our game.

STUFF