Comments
Sort by recent activity
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...
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
Yes, the patch worked for me. Thank you for following up. / comments
Yes, the patch worked for me. Thank you for following up.
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...
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 ...