I just want to point out something there, the performance of a database doesn't only depend on how many tables it has, the design plays a very important rule here.
a short example... Imagine that all the employees information are stored in one table, so this table will have many records. every time an employee wants to access his information the engine will search all over the database to find his key and access the info, meanwhile if the info are separated in several tables with some relation, it would take a great less amount of time to find a record.
To sum this up for you, go talk to the designer of the DB and ask him what system requirement would be suitable for that kind of DB.
|