Has a common identifier table, to which these ten tables belong. This will work well because it will provide unique identifiers, but that does not mean that you could not duplicate the identifier in the table if someone really wants to.
I am referring to a common ID table, which ensures that you do not have duplicates to insert (by adding an identifier to this general table), but the point is to ensure that this never happens, by creating a business rule in the system or by posting control restrictions for cross-referencing other tables (which would ensure uniqueness, but would degrade performance).
source
share