SQL database in a MEF application

Apr 2, 2013 at 1:31 AM
This question is not geared towards an implementation of MEF per se, but suppose I have a WPF application whose features are dynamically composable through MEF. The application is also backed by a SQL database. There are tables and stored procedures that are feature specific, and there are some that are shared across all features...

Should the database always contain all of the supporting objects for all features regardless of whether they are dynamically composed in an instance of the application? I think that would certainly work and be the easiest solution, but is anyone doing anything different?

Any advice is appreciated.