By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,494 Members | 1,502 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,494 IT Pros & Developers. It's quick & easy.

lookup table relationships best practice

P: n/a
What is the best way to setup relationships between one lookup table
and many other tables. The tables did not have any lookup table
relationships which I am adding. One lookup table is used for same data
in several different places.

To use one lookup tables with several tables, I had to disable "Cascade
Update" and only have "enforce relationships for updates and inserts"
checked.

Any pros/cons?

Thanks in advance.
P

Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Lookup table" doesn't mean anything in a relational database. There is only
one type of table.

You define relationships between tables with a foreign key. Unfortunately
SQL Server will only allow cascaded updates and deletes on one key per
table. However, in many cases cascaded updates are undesirable and since
it's fairly easy to code the same you probably won't miss this feature most
of the time.

--
David Portas
SQL Server MVP
--
Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.