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

981 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 […]

5 (2)

You rated this post out of 5. Change rating

2007-08-17

1,848 reads

Blogs

The Evolution of Data: From Databases to Spark to Lakebases

By

The circle cylinder of life Maybe you’ve noticed all the twenty somethings tight rolling...

Why Microsoft Fabric Signals the Next Wave of Data Strategy

By

In today’s data-driven economy, organizations are no longer asking if they should invest in...

PostgreSQL Timeline: History and Evolution

By

PostgreSQL, often referred to as Postgres, is a powerful, open-source object-relational database system that...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Life's Little Frustrations

By Grant Fritchey

Comments posted to this topic are about the item Life's Little Frustrations

When INCLUDE Columns Quietly Inflate Your Transaction Logs

By Chandan Shukla

Comments posted to this topic are about the item When INCLUDE Columns Quietly Inflate...

Visit the forum

Question of the Day

The Updated Columns List

I have this table in SQL Server 2022:

CREATE TABLE CustomerLarge
  (CustomerID               INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED
 , CustomerName             VARCHAR(20)
 , CustomerContactFirstName VARCHAR(40)
 , CustomerContactLastName  VARCHAR(40)
 , Address                  VARCHAR(20)
 , Address2                 VARCHAR(20)
 , City                     VARCHAR(20)
 , CountryCode              CHAR(3)
 , Postal                   VARCHAR(20)
)
GO
If I check the columns_updated() function return in a trigger, what is the data returned?

See possible answers