Just purchased my subscription to your service. Congratulations to you for all your fabulous work!!! Quality is not only outstanding, but a genuine pleasure after frustration elsewhere...

I'm looking for tutorial and best practices for use of multiple databases on multiple portals. Looked but haven't yet found.

Any DNN Creative issue devoted to this yet? Are you planning one? If so, when will it appear?

If in future, any links to FAQs or tutorials found elsewhere?

Relevant issues for multiple databases for multiple portals should address:

-- when and why

-- performance

-- recommended handling of multiple dataconnection strings if one host instance manages multiple portals stored in different databases: Is that even possible with current framework or does that require special customization?

These are some of the issues that come to mind immediately but I'm sure there are others related as well that could be addressed.

Thanks again for your great work!

CT

You can't really handle multiple portals and multiple databases with a single installation of DotNetNuke. It's just not designed to do that.

If you want each website to have its own database, then your solution is to install multiple installations of DotNetNuke. That's the "recommended" method when you are supporting multiple clients as it really does keep the content and membership information separate. And ... if one site causes an installation to fail, it doesn't affect the others.

Hello CT,

Glad to hear the tutorials are useful, it's always good to hear. - Would you mind copying and pasting your comment into the testimonial section of the forum for other users to read?
http://www.dnncreative.com/Forum/ta...fault.aspx

If you have further questions please do not hesitate to ask,

Cheers,

Lee

Hi,

I am also in a position where I have multiple Portals. My WebHost has suggested to ensure a fast site, to put each portal on a seperate Db and therefore DNN install.
Given that, I started the process.
However. I would like certain users of my DNN portals to be able to access the Data on other DNN portals fairly easily.

I have built a 3rd party App, which uses another 3rd Db.
So... for example DNN1, DNN2 and DNN3 plus 3rdPA across 3 Dbs with its own Db.
I want a user from DNN1 and DNN2 to be able to login to DNN3 but not each other.

The 3rdPA would be accessible on all DNN installs, and therefore the Db, however the users from DNN1 and DNN2 need to be able to login to DNN3, but not DNN1 or DNN2 respectively.

Thoughts?

Hello and good day,

I am a part time web manager (not a master) of DNN sites and want to install a separate instance of DNN on the same host. The current database is at capacity (just enough space for log data) and I will have to open several more portals soon.

How does one configure new portals to direct to a different instance of DNN - do we have to start naming folders according the database ? Currently when I create a portal I just leave the folder blank.

How does the web.config change to have to dBAse logins? Can you put two in and a call to the server will try both?

Thanks in advance, Valerie

What you actually want to do is create a separate installation of DotNetNuke. That is, a separate web directory and a separate database. You really cannot have a separate database per portal with a single instance of DotNetNuke. It's just not architected that way.

If you have the resources, separate installations for separate websites is the best way to go.

If you need a more detailed explanation, let me know.