Why would command line execution of an .sdc run significantly longer than GUI execution
russ960
Posts: 1 New member
I'm running a project from the command line using a command like this:
sqldatacompare /Project:"C:\temp\Validation.sdc"
This ran for days (more than 4 days) without finishing. However if I open the same project in the GUI it finishes in an hour or so. Is the GUI using some additional options that I should enable at the command-line?
I'm running 13.8.0.12703.
This ran for days (more than 4 days) without finishing. However if I open the same project in the GUI it finishes in an hour or so. Is the GUI using some additional options that I should enable at the command-line?
I'm running 13.8.0.12703.
Tagged:
Answers
Thanks for reaching out to us regarding this!
The command you are using looks fine to me, so I'm not sure why you would be seeing such a difference in time to run compared with using the GUI.
As a very initial thought, would you mind updating to the very latest version of SQL Data Compare (v.14.7.6) to see if you continue to see this same delay when using the command line (https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_14.7.6.21017.exe)?
Also, would it be possible for you to provide a verbose log file from when the comparison is run via the command line? This may help to show us if the process is getting blocked somewhere along the way.
Dan Jary | Redgate Software
Have you visited our Help Center?