Is it ever a good idea to use a concatenated primary key vs. a surrogate primary key?
There are 2 GUIDs being used as a concatenated primary key & I see that as a red flag...thinking about the "fun" of joining to a concatenated primary key.
To me, it would seem if the table is rarely joined it's not that big of a deal & could conserve space in DB (yes, most DBs you don't need to conserve space...but if you dump it to a remote device it could be helpful to have a small DB). But I still think a surrogate / unique id int primary key is better design.
What do the experts think? Thanks for your help in advance!