Hi Grant

Thanks for the post, very helpful. I definetly didn't know about the 32K+ limit per instance. With this said, I guess we could install several instances, but that would probably complicate things like clustering even more, wouldn't it?

The initial reason we went with multiple dbs is simply because we built this new app from another one which was already using multiple dbs. So, we basically went with the same model for simplicity. In that other scenario, it made sense, because we were only working with a few databases (under 50), and we wanted each db to be isolated so we can treat each client seperatly, provide individual backups quickly, enhance security and things like that.. And, clustering was not needed.

In this scenario, the dbs are much smaller in size, but because we're targeting hopefully have 5000+ users, that would translate to 5000+ dbs, and that number would only grow as we grow our users base. That's why we're revisiting the whole idea while we still have a relatively low number of dbs right now, making the transition back to one db still possible.

Any thoughts?