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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Migrating DotNet NukeMigrating DotNet Nuke
Previous
 
Next
New Post
8/28/2009 11:39 AM
 

Last year, we abaondoned DNN in favor of a homegrown portal for one reason.  It is beyond hell to migrate installations from one Database/server to another.  This is pretty important if you want to have a development enviornment and a production enviornment as any good organization should.

This is many because DNN uses the Idenetity colums as the primary keys on its database.  Since these are generated by the database, an entry in the development database could be 100 and when you copy it over to production, it might get the number 35 assigned to it.  This isn't much of a problem except lots of outher tables are refering to this record and expect it to be 100 when it's 35.

So, to get to my question, has DNN come up with  a simplified way to migrate portals and their data from one database /server combo to another.  I miss much of the functionality and modules on DNN.

 
New Post
8/29/2009 8:26 AM
 

 Hi William,

Although DotNetNuke does not have this feature in itself, the PowerDNN Control Suite allows you to easily migrate DotNetNuke websites from one server to another.  It is not sold as a standalone product but is available as an addon to all PowerDNN Dedicated Servers.

 
New Post
8/29/2009 10:59 AM
 

William,

This issue is a real pain, but it is quite easy to solve (if I understand your scenario).

 

The first case is when you just want to migrate one installation of DNN to new server.

What I do in such case (migrating one DNN installation to another) is

1. Backup the source DB

2. Copy the files of the source installation to the target FTP

3. Create a new DB in the target. Give it the same name of the source DB

(You don't have to give the same user/Pass since you can create a new one and change the web.config accordingly)

4. restore the target DB with the backup file you created from the source DB

5. create a new user (as I said I do not bother with the old one) and password in the restored DB (the target)

6. Change the connection string in restored site's  web.config to have the new user and password as well as the new server address (do not change anything else in the web.config) do it for both connection string in the file

7. If the domain name is changed too  You can also change the value in the portalalias table as needed. Change only the domain name value and keep portals ID.

That's it. start the site in the new location.

If you want to restore a table (not the whole portal) you can read the following thread which I think can give you good insight on how to do it.
http://www.sqlservercentral.com/Forums/Topic478210-338-1.aspx


(I may be off your question, if so, please try making it clearer)
 


Yehuda Tiram
AtarimTR
AtarimTR
972-2-5700114   |   972-54-4525492   |    http://www.atarimtr.co.il
 
New Post
8/31/2009 3:30 PM
 

William Lancaster wrote
 

So, to get to my question, has DNN come up with  a simplified way to migrate portals and their data from one database /server combo to another.  I miss much of the functionality and modules on DNN.

Migrating a database is easy.  Using a development/staging/deployment architecture is not.  There is no simple way to merge databases for DNN, which is what you seem to want.  When you migrate a database, it will replace the original databse with the one migrated in.  In addition, portals are not separate databases in DNN, so migrating a single portal becoomes problematic.

None of this is insurmountable, depending on how much coding you're willing to do, or paid to have done.

Jeff

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Migrating DotNet NukeMigrating DotNet Nuke


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