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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...for core members: upgrade or fresh install?for core members: upgrade or fresh install?
Previous
 
Next
New Post
7/14/2007 12:40 AM
 

i have a few very simple informational sites that run dnn (mostly v 4.3 or so, some on 4.0.2) that i want to upgrade to 4.5.3.  i've tried the upgrade on a few of these and have then proceeded to have to debug multiple problems over what's turned out to be days.  i had hoped the upgrades would be less painful than this. 

i wonder if i would be better off completely deleting the sites and going with a fresh (full) install of the latest dnn framework?  of course, i'd then have to re-create the site, which on some of these simple sites would take a day and probably as much effort as i've put into debugging the upgrade. 

my question is this: in theory, is there any difference between an upgraded installation and a fresh install?  anything significant to be wary of?

other questions: is upgrading just something you need to do more regularly?  does it get less painful as you get more familiar with using the framework?

i'd love to hear someone with a lot of experience share their thoughts on this.  thanks.

 

 
New Post
7/14/2007 3:33 AM
 

there is no difference between a new and an upgraded version regarding files - though there might be a few leftovers from previous versions, especially of modules. This may happen, if the modules are in use and cannot be deleted during the upgrade process. There is another situation for the database: during (nearly) each upgrade and module installation the database structure and some content needs to be modified. Though the core team and the mdouel developers try the best to test the upgrade scripts in different scenarios, there might be situations, where an data definition command may fail and either the structure or the affected data does not get updated properly. Those issues are logged during the upgrade process as text files residing inside the /providers/dataproviders/sqldataproviders. if there is an error reported during the upgrade it is always recommended to check out those issues, as even if the portal seems to continue to work without issues, they may lead into errors on further upgrades or usage.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/14/2007 12:40 PM
 

leupold wrote

there is no difference between a new and an upgraded version regarding files - though there might be a few leftovers from previous versions, especially of modules. This may happen, if the modules are in use and cannot be deleted during the upgrade process. There is another situation for the database: during (nearly) each upgrade and module installation the database structure and some content needs to be modified. Though the core team and the mdouel developers try the best to test the upgrade scripts in different scenarios, there might be situations, where an data definition command may fail and either the structure or the affected data does not get updated properly. Those issues are logged during the upgrade process as text files residing inside the /providers/dataproviders/sqldataproviders. if there is an error reported during the upgrade it is always recommended to check out those issues, as even if the portal seems to continue to work without issues, they may lead into errors on further upgrades or usage.

thanks for the response leupold...

i had assumed from a files standpoint upgrade vs clean install would have no differences (although an interesting side comment are the extra files that are no longer used- are these just wasted space and cannot harm the installation?). 

i was exactly concerned with the database and the tables and data related to dotnetnuke (not modules).  for example, i found that event log entries had changed format, so viewing events from before the upgrade threw an exception.  aside from the tip about the log files in dataproviders/sqldataprovider, are there any other 'gotchas' or things to look out for when upgrading?  do you recommend upgrading consistently to reduce the amount of change (ie going from 4.5.1 to 4.5.3 is less risk / change than going from 4.0.2 to 4.5.3)?

 
New Post
7/14/2007 1:46 PM
 

I agree with everything Sebastian said. I do try a fresh install whenever possible. in my opinion the upgrade process is a miracle because so many things could go wrong but for the most part it works.

It's like Microsoft Windows, sometimes you need to just re-install the darn thing if you can.

One option I do is to create a new site, migrate the users over from the old site then copy over the content and the data for specific modules. For  a huge site this of course is not feasible, but for 20 pages or less it's an option. However I have some sites that have been upgraded from DNN 2.0 and are running fine.

I guess I decide to start from scratch when I know I installed some module that caused problems, then I don't trust the stability of the install and therefore feel that the upgrade is going to fail.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
7/15/2007 1:37 AM
 

AdefWebserver wrote

I agree with everything Sebastian said. I do try a fresh install whenever possible. in my opinion the upgrade process is a miracle because so many things could go wrong but for the most part it works.

It's like Microsoft Windows, sometimes you need to just re-install the darn thing if you can.

One option I do is to create a new site, migrate the users over from the old site then copy over the content and the data for specific modules. For  a huge site this of course is not feasible, but for 20 pages or less it's an option. However I have some sites that have been upgraded from DNN 2.0 and are running fine.

I guess I decide to start from scratch when I know I installed some module that caused problems, then I don't trust the stability of the install and therefore feel that the upgrade is going to fail.

see, none of these sites is very complex- they all use very basic modules & functionality.  in fact, some of the upgrades i've gone through which have had problems are that very type- very basic without a lot of complexity.  that i'm seeing so many problems is what led me to post this topic- maybe i am going about it wrong and need some tips. 

i *can* and will dig in technically if i need to, but i would have guessed upgrades would have been cleaner when dealing with a simple site.  maybe i'm going up too many steps at a time (4.3.4 to 4.5.3, in some cases 4.0.2 to 4.5.3).  i didin't want to be digging through database tables and code when i decided on upgrading. 

i'm toying with the idea of deleting and installing clean for some of the remaining sites i want to upgrade, but the problem with that is that even though they are informational, they tend to have loyal users who don't tolerate a lot of downtime. 

i just wish things were a little more consistent.  or maybe i need to be doing things differently or be more prepared.

i'm open to suggestions.  anyone?

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...for core members: upgrade or fresh install?for core members: upgrade or fresh install?


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