Hey again...  This will probably not be of interest to most.  I'm just putting it here so Dave (the CS guy who helped me out yesterday) can get an idea of where we are if he wants to help me with the upgrade attempt again.

First, a real quick run-down on the upgrade and what happened...  I am running Community Server 2.1 right now, hosted on a shared Windows system, with the database on SQL 2000.  Yesterday, I upped the ASP.Net from 1.1 to 2.0.  I ran the schema update scripts against the SQL databases to bring them up to ASP.Net 2.0 (no problems).  I then attempted to run the 2.1 to 3.0 upgrade scripts.  That's where I started getting Access Denied messages against SQL.  It looks like the last schema update didn't complete, which is probably what killed everything else.  We backed it all out, restored SQL, ASP and my directory and that brings us up to yesterday afternoon.

Last night, I called in to GoDaddy and asked them to move my database over to 2005.  Of course, the answer was "you can't do that".  In other words, it's technically possible, but either they didn't want to or don't know how.  Anyway...  I made a new empty database and verified that it did indeed get created on a 2005 system.  I was then surprised that it allowed me to restore my database from the 2000 backup I did last night.  I checked the 2005 restored stuff and it all seems to be there, but there might be one or two problems that I'll probably need Dave to work on with me...

I have the Schema object under the DB, which was not visible on the 2000 DB.  However, there are now TWO schemas that I think CS might be looking for.  I don't think it's a great idea to go posting my database names for the world to see, so we'll call them Old_DB and New_DB for now.  On the SQL 2005 DB (New_DB) there are a bunch of schema tables, but there are two in particular that concern me when it comes to Community Server.  Within the schema tree, I now see Old_DB and New_DB as schema tables... makes sense, because the new one was built when I made the DB and the old one would have been created by the restore.

So... do the CS scripts care?  Are they doing to pick up the DB and schema names from somewhere or is it a setting I can configure?  Basically, can I convince all the CS scripts to use the old schema table on the new DB?  We shall see... hopefully you'll not be seeing too much cat today. ;)