SQL Compare only accepts splatting if the switch has a parameter.Some characters used in Regex expressions such as pipe (|) cannot be used.Can get long and complicated, difficult to type in.Easily transformed into other formats using XSLT.Allows use of all characters in regex expressions.Easily created and modified in PowerShell.Requires a file for each database for each operation.Supports options not documented in the other techniques.We can summarize some of the advantages and disadvantages of these approaches. I give a run-through of all these in my article Comparing and Deploying SQL Server Databases using the SQL Compare Command Line on Linux or Windows. You could also make a generic task with all the many details that SQL Compare sometimes requires and just fill in the details that change, such as the server, database or credentials, leaving all the other options, switches, and so on, intact. This means that you can create an XML argfile for each task, from scratch, and execute them all on a schedule, maybe. It is not a good idea to generate a project file automatically, whereas the XML argfile is supported. There are several reasons for using XML argfiles to pass in parameters. This is useful if you require a lot of parameters but can’t generate the project file from the GUI. SQL Compare CLI allows you to pass parameters from an XML argument file (argfile), or using a project file, as well as the more usual approach of using switches in the tail of the command line. For full details, see the Changes to distribution of command line page of the documentation. Automations using the SQL Compare command line that require installing it on more than one machine need Redgate Deploy or SQL Toolbelt licenses.
0 kommentar(er)
