Skip to content
  • T-SQL Tuesday #158 – When Worst Practices are the Best
    This month’s #tsqltuesday is an especially interesting one! Hosted by Raul Gonzalez (@SQLDoubleG), Raul asks us to talk about “Worst Practices” and when could they be a good thing to use. I, personally, have a couple of “Best-Worst Practices” that I tend to encounter quite a lot, and have already talked about in some of my blog posts in the past.
  • Detect Application Bugs and Vulnerabilities You Didn’t Even Know About
    In this post, I will introduce you to a special T-SQL script that you can use for detecting potential SQL injection attacks in your database, as well as application-level bugs that you didn’t necessarily know you had.
  • Resolved: Login failed for user NT AUTHORITY\ANONYMOUS LOGON – Delegation Step-by-Step
    Sometimes when trying to access a linked server, you’d get an error saying “Login failed for user NT AUTHORITY\ANONYMOUS LOGON”. This happens because you’re connected using Windows authentication, and SQL Server fails to “forward” your credentials to the linked server. Hopefully, with this blog post, I’ll provide you with an easy-to-understand step-by-step guide, which would help you resolve the issue the right way, without any workarounds.
  • What is not contained in contained Availability Groups
    While being an awesome feature introduced in SQL Server 2012, Availability Groups were always missing the ability to synchronize server-level objects between replicas. This finally changed 10 years later, in SQL Server 2022, with the introduction of “Contained Availability Groups”.
  • Too Many Plans for the Same Query Hash
    In today’s post, I’ll be providing a useful script to detect and troubleshoot when the query plan cache contains too… Read More »Too Many Plans for the Same Query Hash

Follow My Blog

Get new content delivered directly to your inbox.

Other ways to find me:


%d bloggers like this: