Question 940
A marketplace imports orders from three systems and needs an automatically generated surrogate key that does not depend on each source's order code. The team is considering this step: Define a surrogate primary key with IDENTITY and preserve the original source identifier in a separate constrained column. What evidence should they review before proceeding?
Explanation
Correct Answer
Examine source keys, identity seed, primary-key constraint and bulk-import behavior. An IDENTITY property generates values for inserted rows but does not alone prevent all logical duplicates. New inserts obtain unique key values while source reconciliation remains possible.
Incorrect Answers
Successful syntax validation does not expose collisions across the three source systems or prove the imported business keys are traceable.
The current identity counter does not reveal duplicated source orders, source-key conflicts, or whether the reconciliation field is preserved.
A plausible row count can coexist with duplicate commercial orders or an incorrectly defined primary key, so source-key and constraint checks are still necessary.