A week ago, I "bricked" my Community Server database after a failed attempt to update to the latest version.  Sensing that my attempts were futile, I crawled the web in search of a solution, where  I came across numerous posts of GoDaddy users voicing their frustration over failed CS upgrade attempts within the shared hosting environment. 

The main problem we encounter is the inability to run the CS upgrade utility, which essentially updates the database.  Since this application must be executed on the server, shared hosting accounts are limited; however virtual and or dedicated accounts are not.  The only two alternatives we have are to:

1. Reinstall anew, losing all prior data, or
2. Backup the hosted database, download the current CS web folder along with the database backup (.bak), install the web files locally, create a new local database, populate this database with the contents of the backup (via a recovery tool), run the CS update utility, then upload back to GoDaddy .

Far too many steps, for something that could have been addressed via one simple update script.  During my first attempt, I successfully created the local environment and updated the CS site files and database.  The task that proved most cumbersome was sending the database back to GoDaddy.

In a perfect world, you should be able to backup the hosted database, download the (.bak), install, update, backup the newly modified database, upload to GoDaddy, then initiate a recovery; however, this is not possible.  If the original backup obtained from GoDaddy is modified and re-uploaded, the recovery tool will error out, stating that recovery from a modified backup is not permitted, due to security constraints.  In other words, you can only recover backups created on GoDaddy servers.

The next method would be via SQL scripts.  Fortunately the Data Base Publishing Wizard (available here) automated this process by scripting my local database, whilst uploading and executing the update on my remote database. Depending on the complexity of the database, this update can take upwards to 30 minutes; however, if an error is encountered, the update ends and the DB is left incomplete.   This is where I "pan-caked" the site since I could not establish a connection to the database via any direct or indirect method.  GoDaddy techs were genuinely baffled and elevated my ticket for specialized treatment, which was eventually resolved within 24 hours. 

I waited until today, Columbus Day, to try again knowing that I could rely on my day off as a buffer in case I blow it again.  Suffice it to say, my second attempt (second day rather, since I made numerous attempts already) encountered only "one error", which I resolved easily.  This is where I am baffled.  On the first day, I had seven different errors reported; however, after GoDaddy Techs intervened, the trouble was reduced to one minor nuance.  Could my original database have already been damaged?  Or am I too much of a "noob" and should not comment on such matters?  It's probably a little of both, but nonetheless...

YES it is possible to update Community Server 2008 within a GoDaddy Shared Hosting Environment.

Just make sure to do it on an actual or pseudo holiday, since errors are prone to lethargic retreat.

Some of my notes, regarding how to upgrade, are available here: http://andrewbelon.com/digital/forums/t/45.aspx