Re: foreign key references only part of composite PK - table scan issue
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sun, 9 Aug 2009 22:31:41 +0000 (UTC)
Dave (djohannsen2@xxxxxxxxx) writes:
thanks for your efforts, you may have a miscommunication though.
there is only 1 join with 3 tables at play, where an index scan
(essentially a table scan) is at play. i won't explain the table
layouts again though - so no worries. thanks again.
Well, given the minimum of information you disclose, there are
certainly good oppurtunies to leaving things up to our imagination,
or miscommunicaiton, if you prefer.
But it's your call. The less you share with us, the less accurate
the advice.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- References:
- foreign key references only part of composite PK - table scan issue
- From: Dave
- Re: foreign key references only part of composite PK - table scan issue
- From: Erland Sommarskog
- Re: foreign key references only part of composite PK - table scan issue
- From: Dave
- Re: foreign key references only part of composite PK - table scan issue
- From: Erland Sommarskog
- Re: foreign key references only part of composite PK - table scan issue
- From: Dave
- foreign key references only part of composite PK - table scan issue
- Prev by Date: Re: foreign key references only part of composite PK - table scan issue
- Next by Date: Re: foreign key references only part of composite PK - table scan issue
- Previous by thread: Re: foreign key references only part of composite PK - table scan issue
- Next by thread: Re: foreign key references only part of composite PK - table scan issue
- Index(es):
Relevant Pages
|
