Is there such a thing as too many tables?

Question

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

Answer 1

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.)

Answer 2

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.

Answer 3

There is such a thing as too many tables, but 40 is nothing like that number. And when people start butting into product limits, then it's usually the point when they need to rethink their design.

For SQL server, the maximum capacity limits tell you that a DB can contain ~2000000000 tables (if it contains nothing else, has no PKs or constraints of any kind, etc). Needless to say, if you hit this limit, then you're doing something wrong (e.g. you've decided to have 1 table per customer, and somehow you've actually gained a lot of customers)