Products

Solutions

Resources

Partners

Community

Blog

About

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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Can two dotnetnuke application use one databaseCan two dotnetnuke application use one database
Previous
 
Next
New Post
3/26/2008 9:53 AM
 

Hi,

My question is that "Two different dotnetnuke application  can share one database(dotnetnuke configuration database)"

If yes then what is the advantage and disadvantage of it. and how to do it

Thanking you

 

 
New Post
3/26/2008 2:58 PM
 

This is just a guess, but my guess would be yes as long as both applications used different object qualifiers I don't see how it wouldn't work.  However I really don't see any advantage to this.  If it did work it might make maitnence a little tedious because if you where trying to edit something in the database for one of the applications you would have to remember what object qualifier you used and then find that specific table.  I personally think that it would be easier to use a different database for each installation. 

However I am curious to know if using a different object qualifier for both installations would work

 

Hope this helps

Mike

 
New Post
3/27/2008 3:08 PM
 

Why do you need two instances to share a single database? 

Users?   Pages?   Designs?  

What functionality are you trying to achieve?

 
New Post
3/28/2008 11:29 AM
 

Hi Sandip,

Just to add to what the others have already offered... are you aware that DNN is capiable of hosting any number of portals in the same database instance?  These portals can be linked to individual domains (e.g.; www.domain1.com, www.domain2.com) and even individual paths on the same domain (www.domain.com/site1, www.domain.com/site2). 

Make sure you don't do more work than is necessary!

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
3/29/2008 6:27 AM
 

Sharing a database for multiple DNN installations by using different ObjectQualifiers is a feature added in DNN 1 at a time, when Databases were very expensive at hosters. Since this has changed significantly, I don't see a real use case nowadays, except sharing a database with an integrated custom application.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Can two dotnetnuke application use one databaseCan two dotnetnuke application use one database


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