In the scenarios that we are currently envisioning, we are picturing multiple databases for our application.



Each containing a full version of the Tables / Schema / Etc.



Our plan is to have a Base package, then an Specific part per (Customer / System) that we need to integrate to.



Many times we need to integrate to multiple systems on a single server, all w/ the same stuff, just a different package.



We produce add-on packages, so have basically no control over the systems that we integrate to, so if I need to integrate to a Jim1 system than I'm hoping to be able to indicate that, in a single run, the Database name to create and the ERP package.



So develop a solution, all within one DB, Solution1



Need to install it twice, against Jim1Instance1 and Jim1Instance2



Would hope to have a Jim1Instance1_CustomSolution1 DB AND a Jim1Instance2_CustomSolution1 database possible (Schema within the CustomSolution the same, but business rules pointing to different Instances, and views also specific to the Instance)



Not sure if this is possible currently, if going to add probably could allow this as an option within the ToolKit on the Database Level (Prompt during deployment or something), and if selected ask for each DB with this option selected during the Deployment wizard