A) Console application can be invoked by specifying path to the saved project file.
Optional parameters can be used to achieve customizations and logging.
FullConvertConsole.exe projectfile OPTIONS
B) The app can also execute conversions or replications without specifying the projectfile parameter:
FullConvertConsole.exe -OSC "(source connection)" -OTC "(target connection)" OPTIONS
In this case both -OSC and -OTC parameters must be used.
OSC stands for "override source connection" and OTC for "override target connection".
When there is no project file, the app needs this info to be able to connect to the databases.
If you want to specify several parameters, separate each param=value pair with a semicolon ;
Connection parameters (engine, database, username etc.) depend on the database type in question as documented in Connection overrides.
The project type (the type of action) that the app is to perform.
Conversion is described in Full Convert introduction at https://www.spectralcore.com/fullconvert/documentation
Datareplication is described in Replicator introduction at https://www.spectralcore.com/replicator/documentation
Please note that the documentation for the data replication action is listed under the Replicator app, yet the app has been merged into the Full Convert app, but the documentation is still separated.
Log saving strategy, default is Overwrite.
- - Overwrite - log is created or rewritten on each run exactly at the filename specified
- - Folder - in the folder of the filename, new folder with a timestamp name is created, inside of which log is created with the name specified (log filename folder\timestamp\log filename)
- - Timestamp - in the folder of the filename, log is created with timestamp prepended to the file name (log filename folder\timestamp-log filename)
Strategy is global and base folder can be specified for each file or omitted. If omitted, current directory is user as a base folder.
-TABLES <semicolon-delimited list of table names>
List of tables selected for conversion, separated by semicolons. If you want to select all tables in source database, specify * character.
Write summary log file, containing basic information about the conversion.
Log conversion errors.
Log all SQL statements, exactly as they are sent to the target database server to populate the database during conversion.
Log SQL statements sent to the target database server, but just ones resulting with an error.
Log detailed JSON conversion information, containing performance statistics, errors and other info.
Override connection parameter for source database. Exact parameters depend on the database in question. If you want to specify several parameters, separate each param=value pair with a semicolon.
Override connection parameter for target database. Exact parameters depend on the database in question. If you want to specify several parameters, separate each param=value pair with a semicolon.
Override schema mapping. It works exactly the same as mapping in GUI version's Mapping . Separate multiple mappings with a semicolon.
Save project with all overrides included as a new project and immediately exit.
For data replication project, this enables the synchronization. The diff will be applied to the target database.