CLI scenario elements
To execute the command-line interface scenario, you have to create the .xml file. You can find the schema of this .xml file here.
The root element for the Database Compare Suite command-line interface scenario is DatabaseCompareSuiteScenario. This element is mandatory, and every CLI scenario should start with it.
|version||Optional. Specifies the version index of current CLI scenario. The default value for this attribute is 1.0.|
|waitForExit||Optional. Specifies whether the console window should stay open after executing the scenario. The available options for this attribute are true and false and the default value for this attribute is false|
The command-line interface scenario .xml file can include the following elements.
|Connection||Required||Specifies the connection to databases (connection parameters for source and target database can be specified in different connection elements).|
|Operation||Required||Specifies the operations, executed in the command-line interface scenario. Unbounded element. The scenario without any operation is empty and doesn’t make sense. It can be mixed with the ExecuteSql element.|
|Preferences||Optional||Specifies preferences for all operations in the scenario and cannot be combined with the “OpenProject” element.|
|Matching Rules||Optional||Specifies matching rules for all operations in the scenario and cannot be combined with “OpenProject” element.|
|Type Mapping||Optional||Specifies types mapping for all operations in the scenario and cannot be combined with “OpenProject” element.|
|ExecuteSql||Optional||Unbounded element. Specifies the SQL code to execute and can be mixed with the operation element. The value of this element is actually an SQL script.|
|OpenProject||Optional||Specifies existing project to open for the scenario and cannot be combined with “Preferences”, “MatchingPreferences”, “TypeMapping” elements.
It has only one value which is the path to the saved Database Compare Suite project file.
You can find the scenario samples on this page
Didn’t find the answer?
You can report problems, ask questions or share ideas for improvements on our email [email protected].