Optimising read performance by INCLUDEing all columns in index when key is known

Asked Oct 03 '14 at 02:16

Active Oct 03 '14 at 02:16

Viewed 40 times

Say I've got the following table:

FileExtension (PK)
ContentType
ContentSubType
IsAllowable

I know it's always going to be retrieved by FileExtension. Should I add an index on FileExtension and INCLUDE the other columns? I don't care about insert/update performance.

Will such an index perform better for retrieve operations than just a clustered primary key?

I've considered this question but it refers to a scenario where the lookup key is not known.

edited May 23 '17 at 11:46

Community

asked Oct 03 '14 at 02:16

Matt Lyons-Wood

Does your table have a clustered index? If so, what is it? – Ben Thul Oct 03 '14 at 11:33
No, just a primary key (is that equivalent to a clustered index?) – Matt Lyons-Wood Oct 07 '14 at 04:10

Optimising read performance by INCLUDEing all columns in index when key is known

0 Answers0