Let say in a company they have 10 divisions. And they want to have a database that will display, add, edit, search and delete employee info like, name, email, contact, division, etc.
Which is a better design. Creating a database for each division? Or a single database with different tables for each division?
When a single database is created for all the divisions, is it better to create separate table for each division than a single table?
Data Base Structure Question
Moderator: General Moderators
Re: Data Base Structure Question
Definitely one database for all divisions. Just practice good normalization techniques.
For example, each division will have information particular to that division. So you'll want a table specifically for the division and assign an id to each division.
Then, in the employees table, you'll add the division id to that for easy cross referencing.f
And it goes on from there. Start with a good solid design because it's much harder to backtrack and correct than it is to start with a good design.
For example, each division will have information particular to that division. So you'll want a table specifically for the division and assign an id to each division.
Then, in the employees table, you'll add the division id to that for easy cross referencing.f
And it goes on from there. Start with a good solid design because it's much harder to backtrack and correct than it is to start with a good design.