Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2007-03-05 : 10:40:59
|
| Grge writes "Hi, I am trying something completely new to me and am not sure where to start. My boss want a single calog to store all contact information and contact types(Eg..members,vendors,etc) in a single catalog. Then he wants another catalog to be used for a specific purpose..eg Accounting. MY quesiton is what would be the easiest way to join these distinct catalogs into an updatable single catalog via SQL 2000 so I do not need to use an openrowset function every time I want to query or update a record. It might also be important to mention the Contacts catalog holding all contact information will always be joined on 1 of several other catalogs.Thanks,Greg S" |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-03-05 : 11:14:19
|
| seems to me that you're talking about EAV model.google it up.Maybe you should think about implmenting your database in normalized form?Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
|
vladimir.stokic
Starting Member
25 Posts |
Posted - 2007-03-09 : 03:41:31
|
| I agree with spirit1 that you should consider normalization. You do not necessarily have to use the third normal form, but you should keep as close to it as possible. Keep it logical and simple. It is never good practice to mix things that do not naturally go together. |
|
|
|
|
|
|
Multiple catalogs