Text file that contains the SQL statements. Certain categories of SQL statements, such as data definition language, are better suited for use in the command file. Contrast this with a data manipulation statement such as SELECT. A SELECT statement can be used, but the result set is not returned to standard output.

You need a separator character between each command in your command file. See -separator character.

Note: pvddl does not support Unicode characters. If you use Unicode in the command file, pvddl returns the error message: “Cannot connect to the designated server.”

Character used in commandfile to separate SQL statements. The valid choices are any printable character. However, ensure that character does not occur within any of the SQL statements. Common character choices include the pound sign (#), semicolon (;), and at sign (@).

Note: On Linux and macOS, a semicolon separator must be enclosed in single quotation marks. If not, then only the first pvddl statement in commandfile runs successfully. The rest of the statements appear to run without error but are unsuccessful.

Password for the user identified by username

Name of the server on which the database is defined. If you do not specify this option, the local machine is assumed. You may also specify the IP address of the server.

TCP port number on which the database engine running on servername is listening. If you do not specify this option, the default port 1583 is assumed. (Port 1583 is the default port used for the Relational Engine.)

-stoponfail

Stop when the first SQL error is encountered in commandfile. Pvddl returns an error code of PS_E_FAIL if an error is encountered (which equates to -2147467259 decimal). The default action is for pvddl to continue after a SQL error is encountered.

Write output to a file instead of to standard output (stdout). Logfile specifies the name of the file to which output is logged and, optionally, a path to the file. If path is omitted, logfile is created in the same directory in which dvddl resides.