Comments
Sort by recent activity
We are on a range of SQL Server versions, but general keep a year behing microsoft releases, so will be on at least that for recent deployments, and my team have been using that for some internal deployments (eg to test department) also. I have done some testing, and even if its creating a sproc, with the DropAndCreateInsteadOfAlter option it now does IF EXIST -> DROP -> CREATE, which is fine for me. The reason we wanat it is not so much for re-runnable scripts, but that someone may have put that sproc on to a server already as a out of version hot fix (yes, horrid!!), and so it would otherwise fail. Also, we definitely want to override the current version with out proper version. / comments
We are on a range of SQL Server versions, but general keep a year behing microsoft releases, so will be on at least that for recent deployments, and my team have been using that for some internal d...
A useful enhancement to sqlcompare would be to support console output + mirrored output to a log file, not just a results file, so that users can see the output + everything is logged for diagnostics etc. / comments
A useful enhancement to sqlcompare would be to support console output + mirrored output to a log file, not just a results file, so that users can see the output + everything is logged for diagnosti...
I now have 13.7.16.11325 - just upgraded to very latest tracked down the problem! it was because I was using a wtee command to pipe output so I could see the output as well as logging it all. eg: sqlcompare options |wtee -a log.log it was giving the error level of the wtee cmd! I think I will just redirect as normal, and have to output when done!
/ comments
I now have 13.7.16.11325 - just upgraded to very latesttracked down the problem!it was because I was using a wtee command to pipe output so I could see the output as well as logging it all.eg:sqlco...
I too am looking for a consistent way to repeatably use saved options from the cmd line
The options (tables to include/exclude, PKs, columns to include/exclue, etc) will be specific to a database of a particular schema type (and we have 5 or 6 such schema)
It sounds like I cant do this with projects as I would have to create a project per database (and we have many dbs of the same schema), and argfiles have to be set up by hand, which is a shame.
options I have seem to be:
* convert a project to an argfile (eg an XSLT)
* use a project, but somehow override tfs and specific db connection info from the cmd line (string replace!)
* use an argfile, and just face that I must manually create the argfile for each db schema type.
Any suggestions as to which is the best approach, or any other approaches / comments
I too am looking for a consistent way to repeatably use saved options from the cmd line
The options (tables to include/exclude, PKs, columns to include/exclue, etc) will be specific to a database o...
or an automated way of setting up links, as we have ~100 dbs (over 9 environments - TFS branches, test releases, etc), and having each developer do this is wasteful.
I tried to copy the LinkedDatabases.xml, but it gave an error that
"there's no workspace mapping for ..." / comments
or an automated way of setting up links, as we have ~100 dbs (over 9 environments - TFS branches, test releases, etc), and having each developer do this is wasteful.
I tried to copy the LinkedDatab...