Comments
Sort by recent activity
Yep, thanks James. I originally posted here and msdn. Here because it's where i think I *should* ask, and msdn as answers seem to be quicker to appear. / comments
Yep, thanks James. I originally posted here and msdn. Here because it's where i think I *should* ask, and msdn as answers seem to be quicker to appear.
Hi redgate.
Has this been reproduced in-house?
The same results occurred when using the argument xml file with sql compare as well, which after some initial response via email has all gone quiet as well.
If I get confirmation that it' a bug that has no "fix by" date then I can move on... / comments
Hi redgate.
Has this been reproduced in-house?
The same results occurred when using the argument xml file with sql compare as well, which after some initial response via email has all gone quiet as...
ignore my previous post. Obviously *without* the "/include:identical" on the statement the creates the scripts then error 63 is raised when there are no differences in the database. Great. Back to the drawing board / banging my head against the wall... / comments
ignore my previous post. Obviously *without* the "/include:identical" on the statement the creates the scripts then error 63 is raised when there are no differences in the database.Great. Back to t...
Brian Donahue wrote:
If this is the problem I am thinking of, it's not a bug and you should be able to work around it by putting /Exclude:Identical in the command.
Thanks for the reply Brian.
Unfortunately... "Error: The /project switch cannot be used on conjunction with the /exclude switch"
Is there any other way around this?
Does this mean the "preferred" way of using the command line isn't by creating and referencing a project file?
cheers / comments
Brian Donahue wrote:
If this is the problem I am thinking of, it's not a bug and you should be able to work around it by putting /Exclude:Identical in the command.
Thanks for the reply Brian.
...
Ok after a little investigation there are some funny shenanigans going on with the command line arguments, and what causes all these statements to be generated, but at least I have a workaround.
If I run this:
"C:\Program Files (x86)\Red Gate\SQL Compare 10\sqlcompare.exe" /project:"C:\Users\MyUser\Documents\SQL Compare\SharedProjects\redgateprojectfile.scp" /scriptfile:output.sql /password1:password /force /verbose /Options:Default,ForceColumnOrder,IgnoreCollations,oec,IncludeDependencies
then it doesn't create the sp_refreshview statements
But it I then append either of these to the end:
a) "/Report:output.html /reportType:Simple"
b) "/include:identical"
then in each case any change cause sqlcompare to include a sp_refreshview statement for every view in the database, even if the only change was (for example) creating a new table "hello" which has no dependant objects in the database.
Therefore if I run two statements instead, both of which start:
"C:\Program Files (x86)\Red Gate\SQL Compare 10\sqlcompare.exe" /project:"C:\Users\MyUser\Documents\SQL Compare\SharedProjects\redgateprojectfile.scp" /password1:password /force /verbose /Options:Default,ForceColumnOrder,IgnoreCollations,oec,IncludeDependencies
and apend this to the first:
/include:identical /Report:output.html /reportType:Simple
and this to the second
/scriptfile:output.sql
Then I've created my report and output file correctly (without the statements) but with the downside that obviously the build will take longer due to running the statement twice.
Hope this helps someone anyway.
I'll let you raise a bug if you think it needs one, as there's obviously something a bit quirky going on... / comments
Ok after a little investigation there are some funny shenanigans going on with the command line arguments, and what causes all these statements to be generated, but at least I have a workaround.
If...
Hi redgate / anybody.
Any news on this? It's becoming an issue as the scripts are far larger than they should be, and are taking 10 minutes to execute rather than a few seconds, meaning we'd have to manually alter the scripts - removing the point of having it produced as part of the build in the first place, and the validity of purchasing an automation license.
e.g if I create a brand new table "EddiesTable" with no dependencies to any other objects, it still adds sp_refreshview statements for each view in the database, where there really is no need.
For some reason it does this on 2 of our 3 databases in this project. If you have a clue as to what causes this issue to kick in / not lick in I may be able to work out a workaround.
Cheers [image] / comments
Hi redgate / anybody.
Any news on this? It's becoming an issue as the scripts are far larger than they should be, and are taking 10 minutes to execute rather than a few seconds, meaning we'd have t...
Hi Eddie.
The output states
SQL Compare Command Line V10.3.8.406 / comments
Hi Eddie.
The output states
SQL Compare Command Line V10.3.8.406
Thanks for your reply Brian.
For us it looks like the command line is the way to go, even though I currently have a few outstanding issues with it.
We want the build to output scripts, and it looks like the only way to get the TC Plug in to create scripts is via the deployment manager, so we're plugging away without the TC Plug-In. / comments
Thanks for your reply Brian.
For us it looks like the command line is the way to go, even though I currently have a few outstanding issues with it.
We want the build to output scripts, and it looks...