Kimberly L. Tripp

President, SQLskills.com

Kimberly L. Tripp has been working with SQL Server since 1990, and she’s worked as a consultant, trainer, speaker, and writer specializing in core SQL Server performance tuning and availability since 1995.

Posts by Kimberly L. Tripp

Oct 07, 2011

STATISTICS_NORECOMPUTE – When would anyone want to use it?

STATISTICS_NORECOMPUTE stops the database-wide auto-updating (auto update statistics) from updating the specific statistics for an index (or column-....More
Boxer with red boxing gloves
Feb 20, 2011

Dynamic SQL vs. OPTION (RECOMPILE)

Is it better to use OPTION (RECOMPILE) rather than dynamic SQL? Both options are likely to recompile each time, and forcing recompilation with OPTION....More
Feb 13, 2011

Problems with Local Variables

Using local variables in statements and procedures can cause poor cardinality estimates. Alternative solutions can include rewriting the query to use....More
Jan 24, 2011

How Does Index Fragmentation Affect SELECT Performance?

To preserve application architecture, we want to retain the GUID as a primary key when clustering on a new INT column that’s not used by the....More
May 20, 2010

Where does that clustering key go?

I’ve heard that SQL Server stores the clustering key (the columns that define the clustered index) in the nonclustered indexes. Why is that? And is....More
Apr 22, 2010

Changing the Definition of a Clustered Index

I’ve learned that my clustering key (i.e., the columns on which I defined my clustered index) should be unique, narrow, static, and ever-increasing....More
Apr 22, 2010

What Happens if I Drop a Clustered Index?

When a clustered index is created, SQL Server will temporarily duplicate and sort the data from the heap into the clustered index key order (because....More
Apr 01, 2010

Determining the Position of Search Arguments Within a Join

When writing a join, I always wonder if I can improve performance by moving the search argument into the JOIN clause instead of placing it in the....More

Sponsored Introduction Continue on to (or wait seconds) ×