I am reverse engineering a sql server 3rd party app that uses GUIDs as candidate keys. Although they are naturally unique identifiers for rows in the table, they are not - and I cannot make them to be - primary keys (and there is strong physical reason NOT to do so since they are arbitrary random values that would not sort usefully if they were made into pks).
However they do represent “natural” key values and should be defined as foreign keys in other tables. I say “natural” because the values are generated as instance identifiers of objects created in memory and really do represent a meaningful identifier for the objects (and associated data) of concern.
I have not been able to add a non-identifying relationship between two tables where the parent table has a GUID column that is not the primary key. I did add a unique constraint on the candidate key in the parent, but TDM still does not allow me to choose the column as the parent column for a foreign key.
Is this not possible in TDM?