Hi there,

I have a question concerning DNN module developpement. I will have to develop some modules and I want to separate data for each portal.
I will have more than 100 portals with 20-30 modules for each. So I fear that one database will come too big (some modules will store a lots of data). And if there is a crash, or a bad update, all my portals won't work... However, if I have multiple databases, I could dispatch data over n database servers so performance will be better and server crash will impact minimum portals.

So my questions are :
If multiple database possible :
- Is it possible to have one database by portal and one database for the DNN engine ?
- How does it works for module upgrades ? Is there a loop for the n databases ?
- Where can I specify the connection string associated with the portal ?

If multiple database not possible :
- Is DNN designed to support a lots of portals with a lots of modules ? Is there some benchmarking made ?
- How can I extract module data from only one portal and inject that data into another DNN engine ?
- Can I use a module setting to store a connection string for each portal and open connection in my code module, and so, simulate a multidatabase system ? Will it be simple or too complex ?

Thanks for any reply,

Ze Seb

Thanks for your reply.

So it seems that the best solution for my case is to have one DNN core by portal if I want to dispatch the load on many servers. With this solution, I can move a database or the portal where I want.
The only drawback is the upgrade of the core and modules, it will take a lot of time to do it on each portal. Maybe I could make a script to upgrade all my portals in one time...

I think I will follow this direction.

Ze Seb

All portals of a single DNN installations share the same database and I do suggest not to alter this for your module because integrity will become a nightmare. For sure, a SQL database can handle millions of records in a database (SQL Express limits size to 4 GB AFAIR), which shall be sufficient for a large number of portals and users reported of installation with up to 8000 portals, though default management tools are not designed for this size and I usually suggest not to place more than ~50-100 portals in a single installation, as you can easily place multiple installations on the same server.