normalization - database is normalized but the resulting keys are a problem -

But the problem is that there are links that are so large that after becoming normal they have 20 primary keys (composite key ) Which are actually foreign keys

But to help identify the relationship as a primary key, please help? Is it right?

And I apologize for not accepting replies from the specialist community, I did not know that acceptable possible, Tick Mark is showing it: -)

< Never use the overall key. They are a bad technique they are slow and they can be used to keep changing while changing. There is a nightmare.

If you need specialty in two or more areas, then you do not need a primary key, you need a unique index, make PK of the table a surrogate key (preferably int).

If you are trying to create tables with one-to-one relationship, then PK of the parents table is acceptable to use as a PK of the child table and the table Set up a PK_F relationship between; However it requires 20 different one-to-one tables.