Advertisement

01.30.2008 at 01:17PM PST, ID: 23124379
[x]
Attachment Details

Would like to use one base table to generate primary keys for several other tables....

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.3
Tags:

MS SQL 2005

I read an article online not to long ago that described a method in which you could set up an autonumber field in one table and use that field to generate the values for several (or at least one) other tables.  I can't find the article, and I have no recollection of what term Microsoft used to describe this.  
To clarify the idea is such.  We have a contactbase table which generates unique integer values for several other contact tables.  Any one entity may be need to be in one or many of the various contact tables that we have.  i.e.  clientcontacts , customercontacts, personalcontacts etc.  Each table has a set of fields that are particular to the type of information we need to store for the type of contact.  this ofcourse is designed to follow the object oriented paradigm.  Each table represents an inherited form of contact.  One entity may need to be classified as more than one type of contact.  In these cases we need to use the same contactbaseid for the single entity and enter them into multiple tables.

I am looking for instructions on how to tie a PK on one table to to the generated value from another table.

I realize there may be some issues with trying to put the same entity in multiple tables with this approach, but I would like to at least link a few of the contact tables to my contactbase table.

I wish to avoid the use of GUIDs

Currently we are using procedures to manage this, I would rather manage this at the database level.

Thanks in advance for your help!
 
 
 
Expert Comment by angelIII:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Author Comment by chikenhead:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Accepted Solution by angelIII:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
20081119-EE-VQP-45 / EE_QW_2_20070628