Activity overview
Latest activity by jhogan
Yes, the patch worked for me. Thank you for following up. / comments
Yes, the patch worked for me. Thank you for following up.
Looks like this is actually a dup: http://www.red-gate.com/messageboard/vi ... scriptfile / comments
Looks like this is actually a dup: http://www.red-gate.com/messageboard/vi ... scriptfile
Interestingly, SqlDataCompare.exe produces its file when given the same arguments. It even prints "Creating Migration SQL & Saving Script" to stdout. C:\Program Files (x86)\Red Gate\SQL Data Compare 8>sqldatacompare /database1:myDb1 /database2:myDb2 /ScriptFile:"c:\temp\mkddl-out.sql" /force /v
/ comments
Interestingly, SqlDataCompare.exe produces its file when given the same arguments. It even prints "Creating Migration SQL & Saving Script" to stdout.C:\Program Files (x86)\Red Gate\SQL Data...
Sqlcompare.exe doesn't write to file (/ScriptFile)
I recently installed SQL Compare V8.50.12.20 (x86) on a Windows Server 2008 R2 Standard x64 machine.
Everything seemed to be going okay but I don't seem to be able to use sqlcompare.exe to create s...
Thanks for your elucidations. I was able to confirm that that was the problem. I explicitly added all the default options save "IncludeDependencies" and confirmed that this eliminated the unwanted DDL. Thanks a lot.
If I could make a recommendations I would suggest adding this caveat to the /exclude section of the help file because I spent quite a while playing with this trying to get it to work.
Anyway, thanks. / comments
Thanks for your elucidations. I was able to confirm that that was the problem. I explicitly added all the default options save "IncludeDependencies" and confirmed that this eliminated the unwanted ...
Can't /exclude:table
I'm having a pretty straightforward problem. I can't exclude tables using the command line tool. I can exclude stored procedures though. Here is my command:SQLCompare.exe /database1:mydb1 /databas...
I second...
We need this feature because we can make only a limited number of assumptions about the target databases. We can't assume that procs will exists. ALTER's have caused scripts to fail for us in the past because the proc didn't exist.
Is there anyway I can check the status of this feature request? / comments
I second...
We need this feature because we can make only a limited number of assumptions about the target databases. We can't assume that procs will exists. ALTER's have caused scripts to fail for...