The command line supports the following arguments:
| Argument | Description |
|---|---|
| xmlfile | Specifies the xml file that contains comparison settings, such as databases, credentials, options, object exclusion, schema filters and more. |
| /v, /validate | Validates the xml configuration file without performing a schema comparison. |
| /i, /logfile:filename | Specifies the filename where operational messages should be saved. If no log is specified, messages are displayed on the screen. |
| /e, /error:errorlog | Specifies the error log. Depending on the /t option, this parameter could indicate a file or a Windows event log. |
| /t, /logtype:(windowslog) | Indicates the type of the error log. If /t:windowslog is specified, the error log set via /e parameter is considered a Windows event log; otherwise the log is considered a file. By default errors are logged to a file. |
| /o, /overwrite | Indicates whether the log files should be overwritten. By default the command line appends to the log files. |
| /q, /quiet | Indicates the "quiet" mode of operation, which suppresses all messages from being displayed on the screen or logged to a file. |
| /en, /encoding:(UTF7|UTF8|UNICODE|ASCII) | Specifies the encoding that should be used for all output files. ANSI encoding is used if no encoding is specified. |
| /?, /h, /help | Displays the command line arguments. |
The following command performs a schema comparison using the settings in the config.xml file:
xSQLSchemaCmd config.xml
The following command validates the config.xml file:
xSQLSchemaCmd config.xml /v
Apart from /v and /?, all other command line arguments are supported and can be set in the xml config file. We strongly recommend, as a good practice, that you specify the comparison options in the xml config file instead of using the command line arguments. When an option is set via the command line parameter and in the xml file, the command line parameter takes precedence.
Total compare from data to schema with IDERA SQL Comparison Toolset. Learn more > >