Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing DotNetNuke - best practiceInstalling DotNetNuke - best practice
Previous
 
Next
New Post
2/25/2010 4:54 PM
 
Fredrik

Joined: 2/20/2010
Posts: 8

Hi,

I'm brand new to this site so I'm sorry in case this question has been asked before:

I'm currently working on a small Internet company, which is partly focusing on DNN. Of the 500 customers (hosting and webdevelopment), is 30 DNN customers on our server. Currently, these are all in the same installation. So we have 1 installation, with 30 portals. Each portal equals one site.

Now the question I'm asking is: is this the best practice? I talked to a partner today who will start moving his DNN-customers to our servers, and he was convinced that you should have each customer on a different installation. And the main arguments for this is:

  1. In case the customer wants to move to another hosting providers, its easier to move the whole installation.
  2. Easier to upgrade to new versions - what we have encountered now is that we are unable to upgrade to the newest version of DNN because of some modules doesn't have support for another version of DNN. And we can't upgrade until we know for certain that every site will work.
  3. The traffic is divided amongst the different databases/applications.

And there are certainly more arguments for this. I was not in charge of setting up this initial DNN-installation and configuration, but I'm now in charge of the companies future DNN-projects. How do you guys tackle this? And I'm especially asking people who have experience in hosting DNN for several customers.

Thanks in advance for any help in this!
 
New Post
2/25/2010 6:43 PM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

erikvanballegoij.com
Joined: 4/7/2004
Posts: 4445

 we use both approaches, depending on the type of customer. If the site is mainly a static site, with not too many pages and users etc, we put it in a portal hosting environment, otherwise we will put it in its own installation.

Mind you: for small sites, its much more efficient to be running in a larger installation, with multiple portals. DNN caching and the fact that dnn dll's are only loaded once are a big plus. in your case, 30 separate sites will take up much more resources of the server than 30 separate installations.

Yes, there is  a big downside: if you need to move a portal to a separate installation, that can be a lot of work. The way we are doing that at the moment is to make a copy of the complete installation and delete all portals that are not needed.. i am still considering creating a module to do just this... but.. so much to do anyway....

HTH

 

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing DotNetNuke - best practiceInstalling DotNetNuke - best practice


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out