Upgrading from 3.x to 6.
per_malmberg
Posts: 3 New member
Hello!
I'm trying to upgrade our migration scripts going from 3.7.5.328 to 6.
We keep our migration scripts in a separate folder from that which we've linked our db.
In the earlier version you could select a separate folder in SVN for your migration scripts. But I can't seem to find a similar functionality in 6.
According to https://documentation.red-gate.com/soc6/common-tasks/working-with-migration-scripts/upgrading-from-old-versions-of-migration-scripts
SC is supposed to detect my migration scripts and upgrade them to the new format. But when I look at my Commit-tab or the Migrations tab it hasn't detected any of them.
I tried moving the folder containing our migrations scripts into the db-folder but then I got other errors when trying to link the db.
What am I doing wrong here?
Regards/Per
I'm trying to upgrade our migration scripts going from 3.7.5.328 to 6.
We keep our migration scripts in a separate folder from that which we've linked our db.
In the earlier version you could select a separate folder in SVN for your migration scripts. But I can't seem to find a similar functionality in 6.
According to https://documentation.red-gate.com/soc6/common-tasks/working-with-migration-scripts/upgrading-from-old-versions-of-migration-scripts
SC is supposed to detect my migration scripts and upgrade them to the new format. But when I look at my Commit-tab or the Migrations tab it hasn't detected any of them.
I tried moving the folder containing our migrations scripts into the db-folder but then I got other errors when trying to link the db.
What am I doing wrong here?
Regards/Per
Tagged:
Best Answer
-
Mike U
Posts: 316 Gold 1
Yes, in the migrations feature in SoC 5 and later, migration scripts are stored in a subfolder of the main scripts folder, not in a separate repository location. The upgrade process should work as described in the documentation assuming you had the database linked with a previous version of SoC, but it is possible that something has gone wrong in version 6. We'll investigate that and get back to you. We may need more detailed information about the contents of your repository; if we do, I'll ask the support team to get in touch with you directly.
In the meantime, you could try a multi-step upgrade process rather than trying to go directly from version 3 to 6.- First, you should go back to your initial version, 3.7.5.328, and make sure the database is correctly linked to source control, and all migration scripts show up as expected.
- Next, upgrade SQL Source Control to version 5.1.0 (you can download this from http://download.red-gate.com/checkforupdates/SQLSourceControl/SQLSourceControl_5.1.0.2572.exe) and allow it upgrade all migration scripts to the new format. Commit this upgrade.
- Finally, allow the built-in Check For Updates mechanism to upgrade you to version 6.0.2 (or just download it directly from http://download.red-gate.com/checkforupdates/SQLSourceControl/SQLSourceControl_6.0.2.6908.exe)
I hope that helps, and I'm sorry for any inconvenience.Development Lead
Redgate Software
