Foreign Keys are a referential integrity tool, not a performance tool. At least in SQL Server, the creation of an FK does not create an associated index, and you should create indexes on all FK fields to improve look up times.
More Related Contents:
- How do I obtain a Query Execution Plan in SQL Server?
- Count(*) vs Count(1) – SQL Server
- What is the best way to paginate results in SQL Server
- When should I use CROSS APPLY over INNER JOIN?
- INNER JOIN vs LEFT JOIN performance in SQL Server
- SQL JOIN vs IN performance?
- Is a view faster than a simple query?
- Multiple INSERT statements vs. single INSERT with multiple VALUES
- How important is the order of columns in indexes?
- Can a foreign key be NULL and/or duplicate?
- Add Foreign Key relationship between two Databases
- What are Covering Indexes and Covered Queries in SQL Server?
- SQL Server indexes – ascending or descending, what difference does it make?
- Fastest way to remove non-numeric characters from a VARCHAR in SQL Server
- SQL Server: Howto get foreign key reference from information_schema?
- How can I INSERT data into two tables simultaneously in SQL Server?
- Fastest way to determine if record exists
- SQL count(*) performance
- MS SQL “ON DELETE CASCADE” multiple foreign keys pointing to the same table?
- Why is a UDF so much slower than a subquery?
- Favourite performance tuning tricks [closed]
- Can an INNER JOIN offer better performance than EXISTS
- SQL Server SELECT LAST N Rows
- SQL Server 2008 paging methods?
- What’s the difference between a Table Scan and a Clustered Index Scan?
- Slow bulk insert for table with many indexes
- The ALTER TABLE statement conflicted with the FOREIGN KEY constraint
- Two single-column indexes vs one two-column index in MySQL?
- When to use EXCEPT as opposed to NOT EXISTS in Transact SQL?
- can we have a foreign key which is not a primary key in any other table?