Data Base Structure Question
Posted: Mon May 31, 2010 10:32 pm
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?
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?