It says it is a relational database. That means – and this true for ALL relational databases, you have multiple TABLES that are HOOKED together. So for example, ONE table will have ONLY “de-duped” social security numbers and a key and maybe a few other things. ANOTHER table will have various person’s names along with the social security numbers and a key. The field for “social security numbers” in the “names” table would be populated from the table for “social security numbers”. etc. I may have the order of things wrong but as far as the “how it works” goes, Social security numbers ARE ALREADY “DEDUPED” They have to be or the whole thing won’t work right. Because it’s a relational database. Not a flat-file database (which looks like a wide table or an Excel spreadsheet)

It says it is a
relational database. That means – and this true for ALL relational databases, you have multiple TABLES that are HOOKED together.
So for example, ONE table will have ONLY “de-duped” social security numbers and a key and maybe a few other things.
ANOTHER table will have various person’s names along with the social security numbers and a key.
The field for “social security numbers” in the “names” table would be populated from the table for “social security numbers”. etc.
I may have the order of things wrong but as far as the “how it works” goes,
Social security numbers ARE ALREADY “DEDUPED”
They have to be or the whole thing won’t work right. Because it’s a relational database. Not a flat-file database (which looks like a wide table or an Excel spreadsheet)

[responsivevoice_button voice="US English Male"]