Why use a Composite Index in SQL Server

SQL queries can take a long time to run, especially on large tables if not properly indexed. Full table scans can be costly operations when all a user wants is to fetch a few rows based on multiple columns and a WHERE filter. How can we properly index our tables to support multi-column queries?

A Big PK

Managing Underused Indexes in SQL Server Availability Groups – Part 2

Knowing the usage from all workloads is definitely better than focusing on only the primary or a single secondary. But what if I want to make more informed decisions, incorporating row counts, size, and index columns into this output?

Why Indexes are Important Beyond Faster Execution of Queries

Learn how indexes can help you with more than just querying data.

Using Heaps

Index Scans and Table Scans

There are several things that you can do to improve performance by throwing more hardware at the problem, but usually the place you get the most benefit from is when you tune your queries. One common problem that exists is the lack of indexes or incorrect indexes and therefore SQL Server has to process more data to find the records that meet the queries criteria. These issues are known as Index Scans and Table Scans.

What If You Need to Index a Lot of Duplicate Data?

Let’s get a little nerdy and look at database internals.

Index Rebuilds Make Even Less Sense with ADR & RCSI

Accelerated Database Recovery (ADR) is a database-level feature that makes transaction rollbacks nearly instantaneous. Here’s how it works.

How Many Indexes Is Too Many?

Let’s start with the Stack Overflow database (any size will work), drop all the indexes on the Users table, and run a delete:

A Tidy Database is a Fast Database: Why Index Management Matters

Learn about the ways in which you might better manage indexes for a better performing and efficient database.