SQL Server Tuning Blog

Are you experiencing performance bottlenecks? Is this query taking forever to complete? Most DBAs would start their resolution attempts with one of SQL Server’s most powerful features – Indexes. Indexes are such an effective mean that a small change could mean a world of a difference in performance. Most DBAs are also aware that adding indexes will cause some degradation of data modification operations as more indexes need to be updated to reflect the changes. However, few are aware that sometimes adding indexes can be a double-edged sword, with far reaching implications on performance, and not always for the best… This article will help you understand a hidden danger of adding more indexes, that can result in surprising effects on your workload. It tells a story of a production server that was brought to its knees with the addition of a single, innocent looking index.

The SQL Server query optimizer is considered magical by many, even the top professionals. It is an extremely complicated piece of software whose intricate paths and logic are hard to perceive. In this article, the first in a series, We will try to tackle some of the query optimizer’s finer tricks to remove the magical aura and reveal the science underneath.

Writing a query that joins several tables is easy, right? There are just a few major join types and their syntax is pretty straightforward and clear. So how come such a simple join be the source of so many headaches? Why does one query with a simple JOIN take forever and another, similar one a fraction of a second? If you’ve ever wondered what goes on under the covers and how SQL Server implements your joins, this article will help you get started.

If you’ve ever used SQL Trace, STATISTICS IO or any other SQL Server monitoring, you should know what logical reads mean. Or do you? Logical reads server as one of the primary counters for evaluating a Query’s performance. The rule of thumb says “The lower the number of reads, the better the query performs”. I’m sure you’ve heard it before. But… did you notice that in some cases the exact opposite is true? Did you ever see a query improve dramatically in terms of duration and CPU but have it’s logical reads sky-rocket? If you want to understand the TRUE essence of logical reads and be able to tell when it is really a good indicator of performance, I highly recommend you to read this article.

RC stands for Release Candidate, it’s a much more stable and ‘close to final’ version than the previous CTP versions.

Go get your copy from http://www.microsoft.com/download/en/details.aspx?id=28145

This is soooo coooool...

In a previous post, I’ve presented the enhancements to failover cluster instances. In the mean time, Microsoftannounced some radical changes to it’s licensing and editions scheme. In SQL Server 2012, the standard and BI editions will support basic failover clustering of up to 2 nodes.

AlwaysOn Availability Groups

2 days ago, Microsoft announced the new licensing scheme and available editions for SQL 2012.

In a nutshell:

Availability is one of the areas where Microsoft have felt a bit behind the competition. In this release, huge amounts of resources have been spent to catch up.

Although i’m about sum it up in 3 short paragraphs, don’t let that fool you. These are major revisions to the product and are of the highest importance. If you ever needed one of those, you’ll know it.

I’ve recently had the honor of having an article I’ve written being published in one of the most important projects of the SQL Server community IMHO, the MVP Deep Dives II book.

The original MVP Deep Dives book was published in November 2009, you can read more about the original project inthis blog post by Paul Randal, one of the forefathers of this amazing project.

As you probably know already, earlier this month at the PASS Summit in Seattle, Microsoft has announced the official name for the next release of SQL Server, formerly code named “Denali”.

A new SQL Server blog site was born today!

I hope you will find this site as beneficial and interesting at least as much as I intend to.