There are many reasons why we follow best practices. My own reasons have changed over the course of my career. Early in my career as a database developer and then later as a new DBA, I followed best practices because people who claimed to know more about SQL Server said to, and I assumed that their advice would be better than my own. This of course led to me adopting the best practice of not following the advice of someone
I wrote a somewhat popular script and blog post a while back called Breaking Down TempDB Contention. This post explains how to identify tempdb contention. This past Friday, Jonathan Kehayias (blog|@SQLPoolboy) contacted me about the script. Jonathan said that he thought the math was off just a little bit in the script. The original script has the PFS pages repeating every 8088 pages and the GAM and SGAM pages repeating every 511232 pages. That is almost right. The first PFS
My new article for SQL Server Magazine on Hardening SQL Server has been posted online and will appear in an upcoming print issue. This article is a brief explanation of how to secure SQL Server against malicious attack or invasion. This article can serve as a guide for preventing your SQL Servers from being compromised. Excerpt from Article Hardening SQL Server SQL Server applications rely on data, and protecting that data has never been more important than it is today.
What is tempDB contention? From the outside looking in, tempDB contention may look like any other blocking. There are two types of contention that tends to plague tempDB’s, especially when the tempDB is not configured to best practices (multiple, equally sized data files, located on a dedicated, high-speed drive, etc.). For the purpose of this blog, I want to focus on latch contention on the allocation pages. What are allocation pages? Allocation pages are special pages in the data files