The task was to upgrade a site from Umbraco 4.0.3 to 4.7.1.1.
That went ok locally. But (using an sql compare tool) I discovered that the client has since made 158 content changes since the original db backup.
How do I get the new content over to the upgraded umbraco db?
I did a quick db check using sql compare and it seems that there are only a few structural changes. But I've been bitten in the past when screwing with the sql.
So my plan is to take the a new db backup (with the updated content), then run the Umbraco upgrades again.
I'm pretty sure all I need to do is run the upgrade for 4.5.2, to get the db in order. Then I just need to change the connection string in the solution that i upgraded last week to use the new db with new content.
If the client only made content changes perhaps you could use Courier 1.3 for that? Don't know if that will work between a 4.0.3 and 4.7.1.1 version, but it might:).
Upgrading + content changes = hell
The task was to upgrade a site from Umbraco 4.0.3 to 4.7.1.1.
That went ok locally. But (using an sql compare tool) I discovered that the client has since made 158 content changes since the original db backup.
How do I get the new content over to the upgraded umbraco db?
I did a quick db check using sql compare and it seems that there are only a few structural changes. But I've been bitten in the past when screwing with the sql.
So my plan is to take the a new db backup (with the updated content), then run the Umbraco upgrades again.
I'm pretty sure all I need to do is run the upgrade for 4.5.2, to get the db in order. Then I just need to change the connection string in the solution that i upgraded last week to use the new db with new content.
Does that sound reasonable?
Courier 2.0 would be perfect for this, but it only works with 4.5+ so not sure if that's an option.
Jeroen
Yeah the point of upgrading to 4.7.1.1 was to have the new courier and also razor.
If the client only made content changes perhaps you could use Courier 1.3 for that? Don't know if that will work between a 4.0.3 and 4.7.1.1 version, but it might:).
Jeroen
Your first idea sounds reasonable to me...
I'd try that first.
is working on a reply...