Brad McGehee

Brad M. McGehee is a MCSE+I, MCSD, and MCT (former) with a Bachelors’ degree in Economics and a Masters in Business Administration. Currently the Director of DBA Education for Red Gate Software, Brad is an accomplished Microsoft SQL Server MVP with over 13 years’ SQL Server experience, and over 6 years’ training experience.

Brad is a frequent speaker at SQL PASS, SQL Connections, SQLTeach, SQL Saturdays, TechFests, Code Camps, SQL Server user groups, and other industry seminars, where he shares his 13 years’ cumulative knowledge.

Brad was the founder of the popular community site SQL-Server-Performance.Com, and operated it from 2000 through 2006, where he wrote over one million words on SQL Server topics.

In 2008, Brad attended 16 conferences/user group events, presented 26 sessions, and had 1,402 people attend them.

A well-respected and trusted name in SQL Server literature, Brad is the author or co-author of more than 14 technical books and over 100 published articles. His most recent books include “How to Become an Exceptional DBA,” and “Brad's Sure Guide to SQL Server 2008: The Top Ten New Features for DBAs,” and “Mastering SQL Server Profiler.”

SQLServerCentral Article

SSC Clinic: Can Implementing "Optimize for Ad Hoc Queries" Boost Performance for the SQLServerCentral.com and Simple-Talk.Com SQL Servers?

With the introduction of the instance-level option “optimize for ad hoc workloads” in SQL Server 2008, DBAs have a tool to deal with a problem known as plan cache pollution, or plan cache bloat. It’s often caused when one-time use ad hoc queries are sent to SQL Server from Object-Relational Mapping (ORM) solutions, such as LINQ, NHibernate, or Entity Framework. The problem can prevent SQL Server from using its available memory optimally, potentially hurting performance.

(10)

You rated this post out of 5. Change rating

2012-06-14

2,506 reads

Blogs

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array

By

I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...

SQL Server gMSA: Why So Many DBAs Still Aren't Using It in 2026

By

SQL Server gMSA: Why DBAs Still Aren't Using It in 2026 ...

Read the latest Blogs

Forums

Fulltext filter daemon host (FDHost) process has stopped abnormally

By zoggling

We have performed a side-by-side upgrade, from SQL Server 2016 to 2022 Developer Edition,...

Automating OSM Data Refresh in Power BI’s Azure Maps Reference Layer

By Cláudio Tereso

Comments posted to this topic are about the item Automating OSM Data Refresh in...

Database Mail Configuration

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Database Mail Configuration

Visit the forum

Question of the Day

Rebuilding All Indexes

I have added a few indexes to one of my tables in SQL Server 2025:

ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
    PRIMARY KEY (CustomerID);

-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact
After I do this, what will I see for the index status?

See possible answers