Should each app have its own database, or should small apps be merged into one?
- by King
We have a bunch of small to medium sized apps, each of which has its own database (MSSQL Server). There was a suggestion that we consoldate the 'related' databases into a smaller set amount of larger databases.
They don't particularly share a lot of data, they would just be under a similar business group. For example, using a 'Finance' DB to hold the tables and procedures for finance apps.
Would it be appropriate to use a different schema for each app? E.g.
App1.SomeTable
App1.SomeOtherTable
AppTwo.SomeTable
What are the pros and cons of this approach? What should I watch out for?
Thanks