Michael Smith


Technical Article

Prioritize Missing Index Recommendations (2005)

To report indexes proposed by the database engine that have highest probable user impact.  Note that no consideration is given to 'reasonableness' of indexes-- bytes, overall size, total number of indexes on a table, etc.  Intended to provide targeted starting point for holistic evaluation of indexes.

You rated this post out of 5. Change rating

2007-08-17

999 reads

Technical Article

Prioritize Missing Index Recommendations 2 (2005)

This is an enhanced version of my previous script: Prioritize Missing Index Recommendations (2005).To aid in evaluation of whether the recommended index is reasonable, I have added :1. counts for key columns and the total columns of the recommended index  2. the length/bytes for both key and all columns  Note this is 'per row', not […]

(2)

You rated this post out of 5. Change rating

2007-08-17

1,862 reads

Blogs

T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget

By

I am excited to host T-SQL Tuesday for the first time. I want to...

A Daily Report from Claude

By

Redgate had some Claude training recently, which I went through as my knowledge has...

A New Word: Gnossienne

By

gnossienne– n. the awareness that someone you’ve known for years still has a private...

Read the latest Blogs

Forums

Practical Ways to Approach SQL Server Problems and Case Studies

By academicexpertt

Working with SQL Server can involve more than just writing queries. Understanding database design,...

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Importing Excel files into SQL Server using DuckDB and Python

By Cláudio Tereso

Comments posted to this topic are about the item Importing Excel files into SQL...

Visit the forum

Question of the Day

Tracking All the Queries

I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?

See possible answers