I always feel wierd each time I add a new table on my project. If you are using a relational DB, how many tables does your biggest project have?
If you're adding them for justifiable reasons, don't feel bad. I've seen well-run projects with many hundreds of tables.
Don't feel bad, One of my project has more then 1000 tables (crypto-currencies related, one table per coin)
I've worked on systems with 1000 tables in production. It all depends on the complexity of your data model. You need as many tables as you have models in your domain.
97 tables. I don't think it really matters how many you have; as long as it is designed to perform well.
I have about 60 tables so far and many more to come.
Each table has a purpose, holds valuable/relevant data.
Not a project of my own, but rather of a client I was working for. It had about 300 tables in production and was running great because that was what it took for that massive project.
Usually, unless there is a good reason to do so, a large number of tables should make you think about the use cases and serve as early input if you're overdoing something (denormalization is not necessarily evil). However, all this is on a per case basis, so you have to be the judge for it.