shafirmubarak (4/30/2014)
Thanks,For example, user id is used as a linkage across multiple tables.
I am concerned about defining a key for the child tables as it requires 3- 9 columns to make the row unique. Will that be optimal?
Or defining a surrogate key will be of any use?
If 3-9 columns make the row unique, even if you create a surrogate key, you'll still need a unique constraint to ensure the business model is accurately reflected in your data.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning