Modular Application Database Structure

Question

I am building a modular application. Through configuration you can turn these application modules on and off. I'm trying to determine what database structure (mssql2005) I should use for the tables that hold data for each of the modules. The two options that I've thought of are:

1. Put all the tables into one big database and prefix the tables according to the module.
2. Separate the tables for each module into different databases.

I do have data that is common to all modules, so if I use solution 2 I'm not sure how to manage that common data (such as users).

--

To clarify one thing, These modules would potentially be sold separately and the configuration settings are something that are not controlled by the client. This is why I am even considering breaking them into separate tables.

Answer 1

My alternative recommendation to those that you have proposed would be the Schema functionality available in SQL Server 2005.

Please read this link for more info ...

http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1184503,00.html