Dear Group,

I've got several DNN sites on my web host (NewTek). I just upgraded from an ASP.NET 2.0 web hosting account to ASP.NET 4.0. This upgrade included an upgrade from SQL Server 2000 to 2008. I backed up the SQL 2000 database with all of my DNN portals and imported it into a new SQL 2008 database before upgrading to ASP.NET 4.0.

So my old DNN database has been imported in SQL Server 2008 and I took the plunge and changed the settings in the web.config file to point to the new database. Hey! All of my DNN sites come up!

My question now is: will the DNN upgrade path from 4.8.x to 6.1 operate as expected? I mean, I was extra-extra careful to make TWO backups of my on-line SQL Server 2000 database. So I'll make backup(s) of my entire site as recommended. But I'm a bit leery of upgrading because I've already transferred all the DNN stuff to SQL Server 2008. Might there be a hitch if the earlier upgrades expect SQL Server 2000 or 2005?

Thank you in advance. I appreciate it. I'm not doing anything else until I hear from y'all!

Steve Erbach
Neenah, WI

Mr. Connolly,

Doing the upgrade in a test environment could be a toughie...but I'm glad to see that the switch to SQL Server 2008 isn't going to present any show-stopping issues.  I will definitely follow the upgrade regimen.  Might take a couple of weeks to do all of them, but it'll be superb practice! Thank you.

Steve Erbach
Neenah, WI

Steven/Jeff- you dont need to do each and every upgrade step - I often check the prerequisites and if needed apply them (i.e. migrate to the correct sql and .net versions) and then test a jump to a much later version and see if that works - some of the suggested upgrade paths were put in place to catch issues with 3rd party modules/configurations that were later fixed so they're not always necessary (i.e. I've upgraded from 3.3.0-4.9.5 in a single jump and 4.9.3-6.1.0 in a single jump with no issues in the past)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US