Although there is no requirement to do so, one usually creates foreign key
constraints in order to enforce referential integrity. This ensures
Employee or Company City is valid when rows are inserted and updated.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jack" <ja****@humlog.com> wrote in message
news:6e**************************@posting.google.c om...
Hi,
If you have lookup tables which are used by multiple tables (e.g.
'City' lookup table might be used by the 'Employee' and the 'Company'
tables) do we need to link it to both tables? Or can it sit by itself
and just referenced?
Cheers,
Jack