On machines where we still have version 10.4 installed, our migration scripts are being included in the generated deployment scripts. However, on machines that have been updated to version 10.7, these migrations scripts are not being used.

The same command line is being invoked in both cases, and both cases are using the same source and target databases (a SQL Server database and a TFS source).

On the 10.7 machines, we see the "gathering migration scripts" output as the compare executes, but the scripts to do not show up in the deployment script.

I've logged this as a bug (reference SC-7142) and will let you know what I hear about it. It's looking like this will likely be fixed in 11.0 at this point.

This bug is likely to bite me too. Can you confirm whether it's fixed in current v11 betas or whether I should try an earlier v10.x version? If I use an earlier v10 version, will it have any issues with databases coming from the current latest version of SQL Source Control?

I'm afraid I'm a little confused by the versioning of your various products. I'm using the command line version of SQL Compare from a brand new download of the SQL Automation Pack and it claims its version number is v11.0.0.184. Does that mean I'm using a v11 beta version or is the versioning of the automation pack somehow out of sync with the standalone version?

Or, to ask a simpler version of the question - does this version from the Automation Pack have the bug discussed in this post, or not?

I don't know if this is related to this issue or not. I have a saved project that when I deploy through the GUI, migration scripts are included in the deployment. However, if I use the command prompt for that same project, migration scripts are ignored. I look in the log, and see the following error:

The log for using the GUI does not provide this error, so I think the problem is connecting to our source control, which is TFS. I have login information saved on the project. I have also tried providing the scripts and migration scripts folders via xml, and no success. I am using SQL Compare 10.7.0.18.

To be honest, I'm surprised they put that version in the automation pack (it's still in beta), but 11.0.0.184 does contain the bug fix, so it should work fine.

Thanks,Evan

This appears to not be the case: I've just had the first case of trying to deploy using a script generated by that version that was supposed to include a migration script, and it seems not to have done so.

Can you offer any suggestions or an ETA for when a new version with the fix will be available?

Can you send in the details of your issue to support@red-gate.com so we can take a closer look? As far as I know, the bug with retrieving migration scripts in 10.7 is fixed, so perhaps you're seeing a slightly different issue?