|
|
Posted by E B via SQLMonster.com on 10/14/00 11:34
tnx, however i need to implement a distribution lists, e.g
idividual can have 3 phon numbers and 2 lists (inside this list there are
phone numbers and also possible inside this list there are another list)
TNX
Tony Rogerson wrote:
>I'd certainly break the name up into first and last names, probably
>nvarchar(50), also, you'll need other information to uniquely identify this
>individual.
>
>Phone number can be broken up into country code, area code and number as
>well.
>
>Do you need to think about extension number too?
>
>I'd make the phone number (country code, area code, number) a primary key,
>but use a surrogate key to foreign key between the individual and the phone
>number.
>
>So you will have 3 tables...
>
>individual
> other identifying cols...
> first_name
> last_name
> id int not null identity constraint sk_individual unique nonclustered
>
>phone_number
> country_code
> area_code
> local_number
> id int not null identity constraint sk_phone_number unique
>nonclustered
>
>individual_phone_number
> individual_id int not null references individual( id ),
> phone_number_id int not null references phone_number( id )
>
>Tony.
>
>> so this is my question, i need some advice for implementation.
>>
>[quoted text clipped - 5 lines]
>>>>
>>>> TNX
--
Imagination is more important then knowledge. (A.Einshtein)
Message posted via http://www.sqlmonster.com
Navigation:
[Reply to this message]
|