Options
MigrationsFolderXML in SQLCompare 12
DavidBrower
Posts: 3 New member
in SQL Compare
We have a number of projects that use SQL Compare from Octopus Deploy. We have just upgraded to SQL Compare 12 and are now finding that calls to the SQLCompare exe are failing due to the
Can someone please tell me what is the alternative/workaround for SQL Compare 12?
/mfxno longer being a valid switch.
Can someone please tell me what is the alternative/workaround for SQL Compare 12?
Tagged:
Comments
SQL Compare 12 is meant to work with the new migrations scripts model that was released in SQL Source Control 5, which no longer uses a separate migration scripts folder (the migration scrips are stored in a subfolder inside the DB folder). As a result that switch is no longer needed.
If you are using migrations and want to use SQL Compare 12 on that process, you should upgrade SQL Source Control to version 5 and, if applicable, DLM Automation to version 2.
When you upgrade SQL Source Control to version 5 your existing migration scripts will be upgraded as well.
If you don't want to upgrade your migration scripts straight away then you should use the version of SQL Compare you were using before upgrading to 12 (please note that upgrading to version 12 does not replace the old version - it installs version 12 side by side with the old one).
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools