>> Hmm a very interesing theoretical topic...
>> Wouldnt make sense to tie this in with the implementation of a Foriegn
Key?
>> So when the foriegn key is defined you create anoter index that stores
all
>> the relevant child to parent relationships and can be used to speed up
that
>> access since it obviously will be a primary access route (else thay
wouldnt
>> have defined it). I would think it could be used then to check the
Foreign
>> Key integrity and used to help maintain/construct clustered tables...
I read an interesting article a little while back about 'join indexes'. It
was in
a warehousing (again, sic) magazine, and the principle was exactly this. I
think
it's a great idea, although obviously performance becomes an issue.
However, for the
