Schema Compare /Synch Logging

[mango333]

This question is with regards to SQL Server Schema Compare v. 4.0.32

I use this tool primarily at the command line to perform comparisons as part of our DLM process. Currently, I'm working on a way of automating the schema's in our build environment so they match PROD. My idea was to build a bunch of .scomp files and then use a script to iterate through them executing a command similar to the following:

.\schemacompare.exe /schemacompare /compfile:"C:\MyComparison.scomp" /sync

I'd like to be able to log the results of the sync operation, or at least any errors generated. As I understand it, the /Log switch logs the results of the compare operation and not the sync. I looked around in the application and didn't see any settings that would allow me to do this.

Is the Schema Compare, at the command line, capable of generating a sync log? If so, can you provide some direction?

[alexa]

Unfortunately, there is no such a possibility. You can add a suggestion on the UserVoice forum http://devart.uservoice.com/forums/1770 ... sql-server

[alexa]

Could you please specify what exactly you would like to see in the log?

[mango333]

Alexa I submitted the idea as suggested.

http://devart.uservoice.com/forums/1770 ... e-sync-log

[alexa]

Thank you for the reply.

We will try implementing this in one of the next product versions.

[mango333]

FYI...I ran a compare/sync/log at the command line and interestingly enough the log did pick up the sync operations. I had no control over the level of logging, but everything displayed to the console was picked up by the log.

[alexa]

Thank you for letting us know this.

We will take this into account.

[alexa]

We would like to let you know that the functionality you requested is added in dbForge Schema Compare for SQL Server, v4.2 https://www.devart.com/dbforge/sql/sche ... nload.html

Thank you for your help in improving dbForge Schema Compare for SQL Server.

[mango333]

If I already have a license, how do I download the latest version?

[mango333]

I'm testing the latest version 4.2.35 and am running into errors when I perform a compare and synch on the command line, using an argument file. It appears many of the arguments have disappeared completely or changed names. This is going to be a lot of work to true up all of the places I'm using these files. Ugh.

Is there a place that shows what arguments have changed between versions? Or am I going to run file compare and figure it out with new argument files?

[.jp]

Hello,

Thanks for the post.

I'm testing the latest version 4.2.35 and am running into errors when I perform a compare and synch on the command line, using an argument file. It appears many of the arguments have disappeared completely or changed names. This is going to be a lot of work to true up all of the places I'm using these files. Ugh.

Is there a place that shows what arguments have changed between versions? Or am I going to run file compare and figure it out with new argument files?

A lot of new options were implemented in the latest version, so an argument file should be generated anew.
I would recommend use a schema comparison project file (.scomp) instead of the argument file, because the project file is easy to use in the command-line. Please have a look at the documentation.

Best Regards.

[mango333]

Thanks for the response .jp, but this is problematic.

We've been using this product over the past year and have automated processes that use .scomp files in addition to argument files on the command line for various steps in the process. When you completely change how these files work, I need to understand the changes so I can update my code. So the question stands - is there a list somewhere that details the changes in argument files for the update?

As an aside, I've been waiting more than 6 months for this update and still can't upgrade our production instance with this update until I can get all of the generated artifacts fixed. This is quite a big deal for us.

[mango333]

No need to reply; I found the list in the documentation.

[alexa]

Thank you for updating us on this issue. Please let us know if any questions arise.