Restore/repair schema on 2007?

Reply

gduthie Posted: Mon, Apr 30 2007 4:26 AM

rated by 0 users

OK, so I did a fresh install of CS 2007, got it working successfully. I had a separate install of CS 1.0 that was badly broken, due to having been coinstalled along with DNN (long story).

In order to move the posts, I made a copy of the DB, ran the upgrade scripts, and then attempted to use the DTS Wizard to copy over the tables to my CS 2007 install. Needless to say, this didn't work smoothly. In order to get the posts migrated, I had to remove several keys and relationships. Unfortunately, I don't have a good record of what they were. The good news is that the blog appears to be working fine in terms of displaying existing posts, and I can publish and edit new posts. I cannot, however, edit old posts, and would like to be able to do that, since some of the posts have broken links that need to be fixed.

So does anyone know if it's possible to use one of the scripts to restore and/or repair the schema, or at least any missing relationships?

Reply

gduthie replied on Tue, May 1 2007 11:54 PM

rated by 0 users

I was not able to find any answers to repairing the schema, so I decided to start with a new database and try again.

This time, I migrated tables one at a time using the DTS Wizard, starting with the tables that had no dependencies, and then eventually copying over the cs_Posts and cs_Threads tables, which needed to be copied over together as a part of a single operation.

I managed to get all the data migrated, but was having trouble accessing older posts. It turns out that CS 2007 uses the PostName column in cs_Posts to generate the URL for the archived version of a post, and that column was NULL for all of the imported rows. Updating the PostName column using the value of the Subject column solved the problem, and viewing archived posts now works great.

I also discovered that if you have the blog itself set to one timezone, and your user account to a different time zone, you will get some significant discrepancies between when you actually post a blog entry, and when the software says you did. Changing the timezones so they match sorted this problem out promptly.