Search
  • Adam Thurgar
    • Oct 16, 2018
    • 1 min read

Indexes on foreign keys


SQL Server automatically creates a clustered index on a primary key column/s.

You can change this to be a non clustered index if required, maybe there is a better choice for the clustered index.

When you create a foreign key, nothing happens except the building of the PK/FK relationship.

Should creating a FK also create a non clustered index. I think that it should.

This could help query performance, especially joins.


2 views

Recent Posts

See All

Cardinality estimator

Recently I was asked by a software vendor to review a particular query that ran in under a second on a SQL Server 2014 installation at a compatibility level of 110 (SQL Server 2012), but when run unde

4Write a comment

Index fragmentation

A law firm client, occasionally has issues with their legal software, that is provided by the global leader in this field. The response from the software provider is always the same - you have index f

2Write a comment

Deleting large amounts of data

I had a client call me about wanting to delete a large amount of data from their database. They knew what tables they wanted to delete from. They also knew that deleting large amounts of data causes t

3Write a comment