July 23, 2014 at 1:24 am
hi there i am new here and especially to design database aim currently in school
i need help to design wills database that will keep record for will older,
member detail
members spouse
specific bequest
martial status
nominated executor
dependent
devolution of estate
payment
i am stuck this its an idea i have for my assignment.
thank you so much.
July 23, 2014 at 5:25 am
I won't design it for you. I don't get any grade.
Don't think of it as wills and people. Just think of it as things. Some of the requirements you have listed are things. Some are descriptive properties of things. List out what you think the things are and list out the properties of those things. That's step one. Step two, figure out what the relationships are between the things. Are they one to one (might be that you're looking at a property of a thing then), one to many (parent to child or primary key to foreign key), or many to many (the relationships can run lots of ways, for example any one will can have lots of bequests to lots of people, therefore requiring an interim table to map them together). Lay all that out to get started.
Then, if you have a specific question about the details of the work you've done, I'll be happy to help out, as will others here.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 23, 2014 at 5:51 am
thank you for ur reply, but am kindly stuck here,can u elaborate more, i would like to think like a things but this thing have many thing in it,how aim going to organize it?, may be diagram from one to many,single relation or many to many relationship. ohoo how i wish just could be you. thank you
July 23, 2014 at 6:11 am
I'm really not going to do the work for you.
I'll give you a hint to get you started though. There are three items listed above that are people. Figure out what they are. There's the first table I would define. Then, these people have to be related to each other in some way and the relationship can't simply be Parent to Child (in both the literal and figurative sense), so you'll need to define a table to support the relationships. Work that bit out. Now you've eliminated some of the requirements, start working through the rest in the same fashion.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply