•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Database Design section within the Web Development category of DaniWeb, a massive community of 427,202 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,250 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Database Design advertiser: Programming Forums
Views: 1061 | Replies: 3
 |
•
•
Join Date: Apr 2008
Posts: 3
Reputation: 
Rep Power: 0
Solved Threads: 0
Newbie Poster
Hi,
I am making a database and currently trying to normalise it to bcnf, all my other tables i believe i have got correct and work in the best way. However i was wondering whether or not for my Employee table if using bcnf it is wise to try and split up the table?
The table consists of attributes suich as employee id, fname, sname, sex, houseno, street name etc etc and stuff like phone number. Looking at it i feel i maybe could split it up, but im not sure if maybe it would be best to keep it all in one table as it is mainly all contact information as there isnt really anything that applies to projects an employee may be assigned to!
any opinions would be helpful
I am making a database and currently trying to normalise it to bcnf, all my other tables i believe i have got correct and work in the best way. However i was wondering whether or not for my Employee table if using bcnf it is wise to try and split up the table?
The table consists of attributes suich as employee id, fname, sname, sex, houseno, street name etc etc and stuff like phone number. Looking at it i feel i maybe could split it up, but im not sure if maybe it would be best to keep it all in one table as it is mainly all contact information as there isnt really anything that applies to projects an employee may be assigned to!
any opinions would be helpful
•
•
Join Date: Apr 2008
Posts: 295
Reputation:
Rep Power: 1
Solved Threads: 41
Posting Whiz in Training
hi djclipz,
one cannot state anything about your normalisation, if you do not tell precisely of which attributes your relations consist of. As for "suich as employee id, fname, sname, sex, houseno, street name etc etc " what is etc etc? It might be helpful for yourself if you list some functional dependencies.
brs, cliff
one cannot state anything about your normalisation, if you do not tell precisely of which attributes your relations consist of. As for "suich as employee id, fname, sname, sex, houseno, street name etc etc " what is etc etc? It might be helpful for yourself if you list some functional dependencies.
brs, cliff
•
•
Join Date: May 2008
Posts: 53
Reputation: 
Rep Power: 0
Solved Threads: 4
Junior Poster in Training
i will read this tomorrow. i have Normalisation so that i can get a good idea about it after talking here. so tomorrow ill tell what my idea is about this thread. thanks..
•
•
Join Date: May 2008
Posts: 53
Reputation:
Rep Power: 0
Solved Threads: 4
Junior Poster in Training
•
•
•
•
Originally Posted by tesuji 
hi djclipz,
one cannot state anything about your normalisation, if you do not tell precisely of which attributes your relations consist of. As for "suich as employee id, fname, sname, sex, houseno, street name etc etc " what is etc etc? It might be helpful for yourself if you list some functional dependencies.
brs, cliff
|
•
•
•
•
•
•
•
•
DaniWeb Database Design Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Linear Mode
Other Threads in the Database Design Forum
- Previous Thread: DB Design
- Next Thread: how can i understand nontrival can u explaing with example please?
