Be very careful about whom you wish to blame. One cannot expect professional results when explicit directions (in layman’s terms) are ignored.

First of all, there should be no need to recreate any database because you have a complete backup handy. Likewise there should be no reason to reinstall the website from scratch, because a backup copy is readily available. In fact, you should be able to set a single setting in IIS and have your production site back online within 10 seconds.

Honestly now, when is the last time you have actually restored your database from a backup? Professionals can do it blindfolded, while sleeping, with one hand tied behind their back.

I will bet that the majority of SQL Server users have never used _both_ the backup _and_ restore features of SQL Server Manager. Most people just copy DotNetNuke over the old version over the old and hope it works. If it doesn’t they come here and rant and rave about how broken DotNetNuke is because it didn’t work.

Then there’s that other group that seem to have no trouble upgrading at all.

You must also consider that the DotNetNuke v4.x CMS framework is supported by multiple technologies including Microsoft SQL Server (MS-SQL) 2000 / 2005 / 2008, Internet Information Services (IIS) v5 / 6 / 7, Windows 2000 / XP / Vista, Windows Server 2000 / 2003 / 2008,  New Technology File System (NTFS) v3.x / v5.x /v6, Access Control List (ACL) , Visual Studio 2003 / 2005 / 2008 including permutations.

On the other hand you could always move on; and leave it to the professionals.

P.S.: Whenever you point your finger at someone else, you always have three fingers pointed at yourself. (Try it!)