Richard and I talk to the illustrious Kim Tripp in a rare interview without her husband Paul Randal. The conversation delves deep into the wonders of indexes in SQL Server, including the value of clustered indexes, their impact on non-clustered indexes and a huge number of details on why some indexes rock and other suck. Check out Kim’s blog here.

Kimberly L. Tripp is an SQL Server MVP and a Microsoft Regional Director and has worked with computers since 1985. Her career with database technologies began with IBM in 1988 and with Microsoft SQL Server in 1990. Since 1995, Kimberly has worked as a speaker, writer, trainer, and consultant for her own company SYSolutions, Inc. (aka Kimberly is a writer/editor for SQL Server Magazine; was a founding writer for T-SQL Solutions magazine; was a technical contributor for the SQL Server 2000 Resource Kit; and co-authored the MSPress title SQL Server 2000 High Availability.

Kimberly has presented lectures and seminars at Microsoft Tech*Ed and other SQL Server-related events since 1996 and is consistently top-rated both on quality of technical content and presentation style. Kimberly regularly consults with customers to help them tackle their availability and performance issues as well as works with Microsoft to provide new and interesting technical resources including the SQL Server 2000 High Availability DVD. The HA DVD was a great experience where Microsoft funded the recording, production and duplication for a DVD with roughly 9.5 hours of content covering SQL Server 2000 High Availability technology such as log shipping, backup/restore, clustering, and administration. This DVD is available from your Microsoft contact — the part number is 098-96661.

Currently, Kimberly is working to help create SQL Server 2005 (code-named “Yukon”) content including whitepapers, course materials, and labs. Prior to starting SYSolutions, Inc. in 1995, Kimberly held positions at Microsoft including subject matter expert/trainer for Microsoft University and technical writer for the SQL Server Development Team.