Future of command line /argfile switch
We use SQL Compare and SQL Data Compare from the command line and configure options, exclusions and inclusions in xml files which we pass in using the /argfile switch. Comparisons and deployments are all automated which is why we use the command line. I have been investigating how we could introduce more sophisticated data comparisons using WHERE clauses and have noted from other forum posts that this is not available via the command line unless the WHERE clauses are saved in a project file and passed in using the /project switch. I have also noted, however, that the Project options in a saved project are ignored if passed in via /project switch. Also, in the SQL Compare documentation somewhere I noticed that the use of filters are suggested above the use of Inclusions or Exclusions configured in an argument file. My question is really about the direction that Redgate is taking for future releases of SQL Compare and SQL Data Compare. It seems to be implied that the use of XML argument files for the command line is not Redgate's preference. Does this mean that project files and filters are the future and that argument files and other command line switches will eventually become obsolete? If so, is there a plan to fix the fact that project options are ignored if using the /project switch?
0 · Share on Twitter