S
sanjaykb
Guest
Hello forum,
I am new to designing databases and am excited to learn everything I can. I have read about normalization and relational structures and just need some assurance that I’m on the right track. I’m not looking for someone to design this database for me but am looking for someone to help critique what I have so far which is some user requirements and a RSD. My RSD is attached below.
What I am building is a database to track carpets that have been cleaned in rooms which are in buildings.
Employees clean carpets in rooms in a building. Many employees can be assigned to a carpet cleaning project. Employee’s record which building they are in, what room's carpet they are cleaning, what day and time they started and ended cleaning, what materials and method of cleaning they used, and the reason for the cleaning. Depending on the reason, the customer is charged a certain rate per hour of carpet cleaning. I am hoping to be able to query from this database to be able to answer, when the last room was cleaned, how long did it take to clean a room, and how much did it cost to clean a room.
Some questions I have are:
What attributes should be included in the PROJECTDETAIL table and not in the PROJECT table?
When should I create a table showing DETAILS of an entity?
How do I know when I should have an associative table or correlation table?
Am I on the right track in creating this database?
Thanks for your help!
I am new to designing databases and am excited to learn everything I can. I have read about normalization and relational structures and just need some assurance that I’m on the right track. I’m not looking for someone to design this database for me but am looking for someone to help critique what I have so far which is some user requirements and a RSD. My RSD is attached below.
What I am building is a database to track carpets that have been cleaned in rooms which are in buildings.
Employees clean carpets in rooms in a building. Many employees can be assigned to a carpet cleaning project. Employee’s record which building they are in, what room's carpet they are cleaning, what day and time they started and ended cleaning, what materials and method of cleaning they used, and the reason for the cleaning. Depending on the reason, the customer is charged a certain rate per hour of carpet cleaning. I am hoping to be able to query from this database to be able to answer, when the last room was cleaned, how long did it take to clean a room, and how much did it cost to clean a room.
Some questions I have are:
What attributes should be included in the PROJECTDETAIL table and not in the PROJECT table?
When should I create a table showing DETAILS of an entity?
How do I know when I should have an associative table or correlation table?
Am I on the right track in creating this database?
Thanks for your help!
Last edited:
