CS 2007 upgrade status

by smthng 18. October 2007 08:05

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. ;)

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags: , , ,

blog

Sandisk Sansa Express for Podcast listeners - first thoughts

by smthng 16. October 2007 11:53

Hey again... yes, it's the THIRD post by me today.  I'm on a roll, go figure.

I picked up my Sandisk Sansa Express the other day and have been messing around with it.  It's more "bump proof" than my Zune and it doesn't require any funky software, which are the main two reasons I got it. But, it does have some minor issues and I thought I'd pass them along for anyone who's interested.

First, I gotta give props out to AnythingButIpod.com for having a good review of the thing in the first place.   It's pretty much what convinced me to go with that one over a few others.  But, there are a few things that they didn't mention that are important to me... and might have convinced me to go with another unit had I known.

The first issue I found right off the bat...  when you power the thing off, it doesn't remember where you were in whatever you were listening to.  Not a big deal if you're in the middle of a four minute song, but it's a major issue if you're 20 minutes into a 1 hour podiobook.  That kind of bites.  Unfortunately, that also immediately brought the second issue to my attention...

The fast forward is SLOW!  Not the worst I've seen, but I've seen MUCH better. :(  In an attempt to fix this, I decided to see if there was a firmware update. Result?   The third issue...

The firmware update tool doesn't work.  After dinking with it for way too long on three different computers (one of which blue-screened), I managed to get it to work once.  It went out, checked for an update and told me there wasn't one.  Nice.  As of now, the firmware of 01.01.01A2 is current.  If that saved one person from trying to go through the process of getting that silly updater to work, I've done a very good thing.  You're welcome.

Other than those three bits... so far, I like the Express.  I don't "worry" about it like I do with the Zune.  I can toss it in the tank bag or in a pocket with keys and it's no big deal if the back of it gets scratched.  It does what it does and not much else.  It's relatively simple, easy to use and it can take an extra 2GB microSD card.  I'll probably bug Sandisk to see if they can address the issues above in the next firmware update, but otherwise, I'm good with it. 

L8r!

Oh... almost forgot...  All this stands a slim chance of "going away" soon.  I've pretty much convinced myself that I should attempt upgrading Community Server sometime soon, and I'm guessing that GoDaddy's server is gonna barf on me.  Hopefully, I can get it all in there nice and happy like, but there's a chance I'll nuke it.  I *might* convince myself to copy and paste all my entries just to make sure I have them somewhere... but I kind of doubt I'll be that industrious before I decide to jump in head first.  Hey, at least I'm realistic about myself.  ;)

Rly L8r!

Tuesday, October 16, 2007 5:53 PM

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags: , , ,

blog

Powered by BlogEngine.NET 1.4.5.0
Theme by Mads Kristensen

About smthng

Just a guy who digs Jeeps, photography, podcasts, sci-fi, running, motorcycles, and stuff.

Tags