Whenever you have a one-to-many relationship between two tables, you'll have a foreign key reference in the table on the many side of the relationship.
In most database systems, the primary key is automatically indexed; that's not always the case with the foreign key.
To ensure best performance on joins, make sure that every foreign key in the database is indexed. The next candidate for indexing is any column that will be used for sorting — any column that will consistently be used in an ―order by‖ clause of a SQL query.
You'll also want to index columns that will be used for restricting the returned data set, such as those that consistently appear in ―where clauses.
Subscribe to:
Post Comments (Atom)
-
Optimizing SQL Server CPU Performance A number of factors can affect CPU utilization on a database server: compilation and recompilation of ... -
This post contains examples of a number of the most commonly performed DBA activities. They are all listed in alphabetical order by the comm...
-
Move distribution database to another drive: There are scenarios in SQL server Replication that we need to move datafiles and logfiles of di...
No comments:
Post a Comment