Exit codes used in Command Line for /schemacompare

Last modified: January 17, 2025

If schema comparison is run through the command-line interface, the following exit codes are returned depending on the execution result:

Error Code	Description	Additional Information
0	Success	The operation has been completed with no errors.
2	Ctrl+Break	Execution stopped because of a Ctrl-Break.
10	Command line usage error	The command line was used incorrectly. For example, an incorrect flag, or incorrect syntax may have been used.
11	Illegal argument duplication	Some arguments must not appear more than once.
20	Trial expired	The trial period has expired, or dbForge Studio has not been activated.
30	Project file corrupted	Project file corrupted.
40	Server connection fail	Server connection failed.
100	Databases identical	The compared databases are identical or no objects have been included.
101	Databases not identical	This is returned when the source and target are not identical.
105	Resource unavailable	A file is missing.
106	I/O error	This is returned if Schema Compare attempts to write to a file that already exists, and the `/force` switch has not been set.
107	Failed to create report	The report has not been created.
108	No objects to compare	There are no objects for comparison.
112	No objects to sync	There are no objects for synchronization.
114	Error reading objects filters file. Object filters are not loaded	This is returned when an error is detected in the filter file.

Note

The 112 exit code may also occur in the following cases:

The source and target schemas are identical, which means no differences were detected during the comparison process.

Filters were applied during the schema comparison, excluding all objects with differences, leaving no objects to synchronize.

Synchronization options or settings excluded specific object types or changes, leaving no objects to synchronize.

The comparison was limited to a specific scope, for example, certain tables or schemas, and no differences were found within that scope.