Sad.  It seems you have no known-good db...

Doesn't help you much now, but things I do to play safe...

I always make/keep a backup of my DNN package installs (GoDaddy allows 2 on Deluxe hosting) on my own, since it really doesn't take much space.   That is stressed over and over in Chris Hammond's 'procedure' I use...  

GoDaddy backs up your db daily but you can only access the latest.  You can make one user-controlled backup [of each db] that only gets overwritten when you overwrite it.  I make a new backup just before I do any upgrade or db work.  [I also use my second db as a backup, too.  I actually use the second install as a total mirror of production.  Saved my bacon a few times.  I'm anal.]

I should note you can only cross-restore (restore one db from the other one's backup) using the user-created backup...

I certainly don't mean to preach but GoDaddy requires you take safety into your own hands wrt DNN.

Bob H.

With no known-good, or even running db, I don't see what choice you have.  With a working or known-good db there is a chance.

If the work to rebuild is not that great, that makes the decision easier.

Another thing I find invaluable but did not mention before is the Portal Export feature of DNN (must be logged in as HOST), WITH CONTENT.  Some sites and situations make that a better upgrade path.   I wound up with a 'corrupt' db that kept causing more and more problems with each new DNN version a year or so ago.  Portal Export and then import to a fresh install brought nearly everything.  [It cannot bring user credentials, etc.]  

Bob