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.

 All Forums
 General SQL Server Forums
 Database Design and Application Architecture
 Database Design

Author  Topic 

dewacorp.alliances

452 Posts

Posted - 2009-02-10 : 04:51:05
Hi there
I would like to have an input regarding the database design with SQL Server 2005. We woule like to track dynamic data movement about "Client" which is potential have a profile dynamic data containing "Salary", "Accomodation Type", "Family Composition" , "Marital Status", "Address" as well static like DOB, First Name, Last Name.

Should I break down this my two tables: Clients (static data) and ClientProfiles (dynamic data). The relationship will be: Clients has 1 to MANY with ClientProfiles.

What do you think about this design? Any suggestion?

Thanks

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-10 : 20:19:17
Why Dynamic?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-02-10 : 20:23:56
Yes I would break them down into multiple tables. I'd use three tables. The first table would be your static table. The second table would contain a row for each type of dynamic data, I'd call them attributes. And then the third table would link the first and second tables together.

Client, ClientAttr, ClientAttrVal

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -