I\'ve been searching stackoverflow for about an hour now and couldn\'t find any topics related, so I apologize if this is a duplicate question.
My inquiry is this. Is th
In my own job i have about 60 tables and it seems not much) I think that main thing is how datastore organized (relations beetween tables, etc..), how much queries you need to retrieve needed information and how simple you data can be represent as buisness objects in your application.
It really depends on the complexity of the application you're trying to implement. Things such as accounting systems are pretty intense had easily reach 40+ tables.
2147483648 tables or more might be problematic with some engines. 9223372036854775808 tables or more might be problematic with certain others.
(But if your question meant whether there exists a certain number n such that a database design with >n tables must necessarily be flawed, then no.)