I have a wrestling site that I developed several years ago.  It allows club administrators automate the tasks of running a wrestling club.   The site is used by 10 different wrestling clubs. I would like to move the .net code I wrote for this site into dnn to take advantage of the functionality of a mature .net cms

 I've been studying dnn for the last couple of weeks.  I have figured out how to install dnn 8, how to write modules, and a decent understanding of how to configure dnn.  I still have a lot to learn, but I think I'm ready to begin converting my .net site into dnn for increased functionality. Before I get started, I have some questions:

1. What are the advantages of adding multiple portals in one install vs creating a new install for every site?

2. Do I need to worry about the database size with multiple portals?

3.  As far as module development, I have a lot of code that is dependent on multiple tables.  For example I have a club parms table that is referenced by numerous pages.   In my previous code, I have created multiple classes that are consumed as needed. How should I write my modules, so that I can access data from other tables? 

 

Hi Les,

Multiple 'DNN Portals' needs only one database as opposed to 'DNN Installations'. Each 'DNN installation' needs separate database, but there is an exception because at the DNN installation process you can specify a db prefix, this allows you to put multiple DNN Installs in one database (db objects will have different prefixes).
In my opinion one 'DNN Install' with multiple portals is easier to manage. What is important DNN extensions/modules usually has licenses per one 'DNN Install', and license can be reused across all DNN portals, so you pay only for one license.

By default DNN is designed to have multiple portals and it does not affect significantly on the database, so you don't need to worry about the db size if you have multiple DNN portals. Instead multiple 'DNN Installs' will need much more space.

Hard to answer to your last question. DNN module has a data layer that can connect to the db, and all their tables through: stored procedures or micro-orm called Peta-Poco. Reference:
http://www.dnnsoftware.com/community-...

Sharing a single database for multiple DNN instances was a feature in DNN 1 and 2, when databases were really expensive. In DNN 3, the aspnet membership component was included, which does not support objectqualifiers and the feature stopped working. You may still use an objectQualifier, if you share the database with a 3rd party application, to avoid name clashes for common objects.
Multiple portals in a single DNN installation share the user base and may reference existing content (using the Website Group feature). Outside a group, each site has its own security, content and resources. It might be used to reduce administrative costs, typical use cases are a number of small websites being sold individually or a corporative site with child sites for each department of a company.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN