Command-line switches

This topic provides a detailed description of command-line switches and examples of how to use them.

Command-line usage

To view the list of switches for /dataimport, type the following command:

dbforgesql.com /dataimport /?

Note

To run dbForge Studio CLI commands, open Command Prompt and navigate to the folder that contains dbforgesql.com. The default path to this executable depends on where dbForge Studio for SQL Server is installed. If you installed dbForge Studio:

  • As a standalone tool
"C:\Program Files\Devart\dbForge Studio for SQL Server"
  • As part of the dbForge Edge bundle
"C:\Program Files\Devart\dbForge Edge\dbForge Studio for SQL Server"

Available command-line switches

Name Description
/connection Specifies the connection string.
Usage: /connection:<connection_string>
/create Creates a new table for the imported data.
Usage: /create
/errormode Specifies the application behavior when encountering an error.
  • Ignore – Ignores all errors and continues execution.
  • Abort – Cancels execution if an error occurs.

      • Usage: /errormode:<ignore|abort>
/exitcodes Displays the list of exit codes returned by the command-line operation.
Usage: /exitcodes
/inputfile (Unavailable for the ODBC format) Specifies the path to the file containing the data you want to import.
Usage: /inputfile:<filepath>
/inputtable (Available for Access and ODBC formats) Specifies a table or a view to import the data from.
Usage: /inputtable:<tablename>
/password Specifies the server password and overrides the value from the /connection parameter.
Usage: /password:<pw>
/table Specifies the target table for the imported data.
Usage: /table:<tablename>
/templatefile Specifies a data import template file (.dit).
Usage: /templatefile:<filepath>
/treatwarningaserror Specifies the behavior for treating warnings.
  • Yes – Treats all warnings as errors, and the subsequent behavior is determined by the errormode option.
  • No – Ignores warnings and continues executing the command-line script.

      • Usage: /treatWarningAsError:[Yes|No]