If you are using a single DNN installation with multiple portals, they will automatically share a single installation (make sure, only you, the host, gets direct access to the database). If you provide individual installs per client, you'll need individual databases (multiple DNN instances sharing a database using object qualifier is no longer supported since they can't properly share membership tables out of the box).

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

So (let's say) you have:
* 1 DNN (host) install
* 2 portals: 1 for each company (1 and 2)

Normally when you install a module, SQL scripts are run that create the database. This would be one database for all modules within that DNN installation (if I'm not mistaken). In your module you make sure that users (and thus companies / users of different portals) can't see each others data. So the basic approach doesn't let you create a different database for each company.

What you could try to do, is during your install, let the SQL scripts create a database in which you register the different databases used by each portal. You would have to have a setting in your module telling the module the name of the database to save the data in and some code that creates that database. I've no experience in such a setup, so I don't know if you will be able to pull this of and what you will run into. Please let me know if you are able to. Maybe Sebastian knows if this is a viable route?