Error 845 Time-out occurred while waiting for buffer latch type 4 during DBCC CHECK
How could different unrelated tables fail with a latch timeout on the exact same page?
And aren’t latches supposed to be, like, super-quick?
How could different unrelated tables fail with a latch timeout on the exact same page?
And aren’t latches supposed to be, like, super-quick?
In many SQL Server environments, DBAs configure SQL Agent jobs with retry attempts (which is a smart move to handle transient issues gracefully). But with it comes a hidden pitfall that often goes unnoticed:
Retry-enabled job steps can silently overwrite logs.
And improper output file settings can cause runaway file growth.
The culprit? Improper use of append settings and missing time-based tokens in output file paths.
Read More »Hidden Risks in SQL Agent Job Logging: How Retry and Output Settings Can Compromise Your LogsPreviously known as the SQL Saturday branch in Israel, Data TLV is an annual in-person conference for Data professionals and enthusiasts.
The next event will be taking place in Rishon Le’Zion on Thursday, May 8, 2025.
I will be presenting my own session there: Database DevOps for Leaders.
Read More »Going back to DataTLV in 2025After configuring an Email subscription, the subscription result shows: “Failure sending mail: One or more errors occurred.“. In this blog post I will share how I investigated and resolved one such failure.
Read More »Reporting Service Subscription: Failure sending mail: One or more errors occurredDeadlocks in SQL Server can be frustrating and can cause significant performance and reliability issues. A deadlock occurs when two or more transactions are waiting for each other to release a lock on a resource, resulting in a situation where no transaction can proceed, and eventually, one of them is automatically killed and rolled back. This can happen when two transactions try to access the same data in a different order or when one transaction holds a lock on a resource while waiting for a lock held by another transaction. In this blog post, we’ll discuss how to troubleshoot and prevent deadlocks in SQL Server.
Read More »Resolving and Preventing Deadlocks in SQL ServerTraditional database integrity checks in SQL Server can be time-consuming and resource-intensive, especially for large databases, even when using super cool tools like Ola Hallengren’s maintenance solution.
To address this challenge, I developed a TSQL script for performing incremental integrity checks, which significantly optimizes the process and reduces its impact on the server.
Read More »Incremental Integrity Check for Large DatabasesI know it’s a bit of a short notice, but I’m posting this as soon as this became final and publicly announced.
I’ll be delivering one of my newest sessions on the topic of Database DevOps in this year’s GroupBy conference on October 29th: Database DevOps for Leaders
Read More »Catch me live in GroupBy on October 29!This month’s #tsql2sday is hosted by Malathi, a.k.a Mala, a.k.a diligentdba (b), and asks us about how we manage our database code.
Well, as the de-facto DB DevOps expert over at Madeira Data Solutions, I felt obligated (and obliged) to participate and contribute my piece.
Read More »T-SQL Tuesday 177: Managing database codeIt’s been a while since my last post about SQL Server performance optimization. This one focuses on index design and how the order of columns in your indexes can make or break your database queries. Using my insights from real-world consulting experience, this guide should help you understand the critical decisions that would impact your database performance.
How does SQL Server decide where to look first when executing a query? The answer lies in the structure of your indexes. Learn how the sequence of key columns can optimize your data retrieval, making your database faster and more responsive.
Read More »SQL Server Index Mastery: Choosing the Right Column OrderHey there, pull up a chair, and let’s have a real heart-to-heart about what we all know has been happening this past decade in the world of DBAs. Yeah, I know, not exactly what you were looking for in my mostly technical blog, but stick with me here because this talk we’re going to have… Is very, very important.
You see, in this past decade or so, we’ve all noticed a trend where more and more businesses are looking for DBAs who know a bit about everything: RDBMS, NoSQL, Key-Value databases, Cache Databases, Full-Text Search Databases, Vector Databases, and more. In response, more and more data professionals prefer to become multi-disciplinary, doing a bit of everything… Even if it means becoming a part-time Data Engineer / Data Analyst / Data Scientist / DevOps / whatever. Otherwise, they fear that they won’t be able to find enough job opportunities.
But, there’s a cost to that approach. Sometimes a very high cost.
Read More »We need to talk about the elephant in the room – the future of DBAs