Comments
6 comments
-
It sounds like everything is working as designed. It says this is true in the documentation at http://www.red-gate.com/supportcenter/C ... _in_the_cl•When you use the command line, your project option selections are ignored and the defaults are used. Use /Options to specify any additional options you want to use with a command line project.
-
I'm not referring to the /Options switch, I'm talking about the actual selected objects (table / sprocs).
which in the previous bullet point in the documentation:
"When you use a project, all objects that were selected for comparison when you saved the project are automatically included."
Especially since you cant use include/exclude with the /project switch, it would seem that the selected objects should be picked up from the scp.
What would be the point of being able to specify a project file at the command line if nothing is actually used from the file? -
Sorry for the misunderstanding. I'll see if I can figure out what's gone wrong with SQL Compare.
-
Thanks for reporting this. I have logged a bug, SC-6040. SQL Compare is not behaving as it should with regard to saved selections.
-
There is a very-beta patch to SQL Compare out now, if you want to try it:
ftp://support.red-gate.com/patches/sql_ ... 0.1647.zip
It is designed to fix this problem with the command-line, but may well cause additional harm. -
This issue is fixed in the latest SQL Compare 10.7.
Add comment
Please sign in to leave a comment.
Running from the Deployment wizard (SQL Compare UI) generates the correct script (only the objects i selected).
Using the /Project option at the command line generates scripts for all objects. (i only used the /Project switch, no other switches)
Sorry if this question has already been answered, but i did some searches and couldnt find an answer
Thoughts?