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 |
|
brncofan7
Starting Member
3 Posts |
 Posted - 2005-08-09 : 10:33:06
|
| This is probably a pretty easy/basic question, but it's something different than I've approached before. I've done plenty of Customers/Orders/Order Detail designs before, but this one entails a little more detail and I'm just looking for suggestions on how best to approach the design.The customer would be selecting some option. Based on the options selected, they would be presented with a list of available items. So, database would look like the followingYou have an Item, which has multiple Detail Items, but each Detail item, could also have multiple options. This is where I'm getting hung up one how best to approach the design and was hoping for some suggestions. I've thought about creating a master table for the Item and one for the Detail, but should I create tables for the sub-Details?Appreciate the help,Dan |
|
|
Seventhnight
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2005-08-09 : 10:41:58
|
what kind of options?like colors?or various sizes?i would probably say... don't create another table for the sub-details... but it may depend on exactly what kind of info we are talking about here...Corey Co-worker on The Wizard of Oz "...those three midgets that came out and danced, the freaked me out when I was little. But they are ok now."  |
 |
|
|
brncofan7
Starting Member
3 Posts |
Posted - 2005-08-09 : 10:57:12
|
| It's a loan program selection. So, it will be storing basic info about different loans. Problem is that a loan could have multiple "lien positions" (i.e. Loan 1 could have a "lien position" of First or Second Mortgage), and each "lien position" could have multiple "purposes" (i.e. Loan 1 "position" of First Mortgage could have a purpose of "Purchase, Construction, Cash Out, etc.").So, I could create a table of basic info about the Loan and one for each of the "Lien Positions" associated to the loan (in an order/order details fashion), but what about the "Lien Positions" associated data?Hopefully that explains it a little better, sorry about that.Thanks,Dan |
|
|
|
brncofan7
Starting Member
3 Posts |
Posted - 2005-08-16 : 10:38:17
|
| I know this is a few days old, but I need to *bump* it.Anyone? |
|
|
|
rockystar
Starting Member
3 Posts |
Posted - 2005-08-16 : 11:03:12
|
| Follow the rules of normalisation:Loan has 1 to many relationship with lein_positionslein_posistions has 1 to many relationship with purposethat suggests 3 tables to me, you can always use a view to pull them back together for your front end. |
|
|
|
|
|
|
|
|
Database Design Question