Best Practice for FKs and indexing property

[PrincessApril]

For indexing my tables, I'm thinking of setting no duplicates for all the PKs. I'm wondering if it really matters for the FKs, given that they are derived from the PKs, but is there a best practice (no duplicates for good measure?).

[June7]

PK's have to be no duplicates. Setting FK's as no duplicates means a 1-to-1 relationship. This is not a common design. Why would you have 1-to-1 relationships?

[PrincessApril]

Ah, I see.

I suppose I should choose Yes (Duplicates OK) to have indexes for all my FKs? Perhaps it's not necessary, but it seems better than not having the index.

[June7]

Yes, that is appropriate.