Skip to content

Commit

Permalink
Update website/docs/terms/surrogate-key.md
Browse files Browse the repository at this point in the history
Co-authored-by: Grace Goheen <[email protected]>
  • Loading branch information
matthewshaver and graciegoheen authored Dec 7, 2023
1 parent c11032e commit ca9395f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/terms/surrogate-key.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ After executing this, the table would now have the `unique_id` field now uniquel

Amazing, you just made a surrogate key! You can just move on to the next data model, right? No!! It’s critically important to test your surrogate keys for uniqueness and non-null values to ensure that the correct fields were chosen to create the surrogate key.

In order to test for null and unique values you can utilize code-based tests like [dbt tests](/docs/build/data-tests), that can check fields for nullness and uniqueness. You can additionally utilize simple SQL queries or unit tests to check if surrogate key count and non-nullness is correct.
In order to test for null and unique values you can utilize code-based data tests like [dbt tests](/docs/build/data-tests), that can check fields for nullness and uniqueness. You can additionally utilize simple SQL queries or unit tests to check if surrogate key count and non-nullness is correct.

## A note on hashing algorithms

Expand Down

0 comments on commit ca9395f

Please sign in to comment.