My client has royally screwed up his dotnetnuke site and it is unfixable. Is there a way to extract his portal from the database and transfer it to a new installation? I figure I will have to backup his individual portal folder and then transfer over the database tables for any modules that he has installed. What other tables would I need to transfer? Alternatively, is there a utility someone has written that can connect to the database and do this for me?

 Hey David,

 we actually have a tool that is part of our Control Suite application that can do that, however, from what you've said, it sounds like you wouldn't actually fix anything - you'd just replicate the problem.  When you're working with DotNetNuke, it is generally best not to think about the actual tables since, as sebastian mentioned, when you do portals, everything is heavily interleaved, but instead to think about "objects" - our Control Suite operates on the object level and can do portal extractions with extremely good accuracy.  However, if you have custom / third party modules, it may leave some "artifacts" in the database that really should belong to another portal.

Hi,

So the process isn't exactly extracting a portal from a database, it's more like deleting the ones you don't want. (After a full backup and restore).  Is this right?

Rod