Service Pack 3 is now available; the build is 13.0.6300.2 and there are 43 enhancements.
Category: SQL Server
In this tip, I discuss one way to help avoid infinite loops in common while loop patterns.
An index of over a decade's worth of posts and videos involving bad habits and best practices in SQL Server.
In part 4, I show how to include ad hoc DML queries in the analysis.
In part 3, I tie it together and show how to use relational logic to further eliminate false positives.
SQL Server 2019 Cumulative Update #12 is available, with 40 enhancements (29 public). The build number is 15.0.4153.1.
In part 2, I show how to identify problematic NOLOCK patterns across multiple databases and multiple instances.
I start a new series on identifying and removing problematic NOLOCK hints from update and delete statements.
For T-SQL Tuesday #140, Anthony Nocentino asks us what we have been up to with containers.
I explain why you should eliminate the data types text, ntext, and image from your environment.
After thinking setting up SQL Server 2019 on CentOS 7.5 was going to be a piece of cake, I explain how my team helped resolve a TLS issue preventing remote connections.
SQL Server 2019 Cumulative Update #11 is available, with 62 enhancements. The build number is 15.0.4138.2.
In this part of my "using a calendar table" series, I talk about filling gaps and identifying gaps and islands.
It seems a lifetime ago I wrote about creating a calendar table; now I've started a new series showing how to use the calendar table. In the first installment, I deal with business day problems.
SQL Server 2019 Cumulative Update #10 is available, with 63 enhancements. The build number is 15.0.4123.1.
SQL Server 2016 SP2 Cumulative Update #17 is available, with 20 enhancements. The build number is 13.0.5888.11.
I use a real-world example showing why you shouldn't use deprecated functionality like SQL Server Profiler.
In this tip, I talk about cases where SQL Server will interpret YYYY-MM-DD as YYYY-DD-MM, which is less than optimal.
I talk about one scenario where the system table
sys.sysprocesses almost led us down the wrong path.
After seeing this question pop up on forums multiple times, I wrote a quick tip about enforcing unique constraints where order doesn't matter.