## SQLWays - Command Prompt Options

You can run SQLWays from a command prompt. Before using SQLWays in the command prompt, open a command prompt window (cmd.exe on Windows NT/2000/XP or command.exe on Windows 9.x). Then set options and run SQLWays.exe.

The following chapter describes available command prompt options.

SQLWays.exe /D = DataSourceName [/U = UserName] [/P = Password] /T = TableName or /S = SelectClause or /SF = SelectClauseFile or /TF = TableListFile [/V = ViewName] [/SP=StoredProcName] [/FN=FunctionName] [/TG=TriggerName] [/EXC = ExcludeColList] [/SROW = StartRow] [/CNROWS = NumRows] [/TARGET = TargetDBMS] [/TVER=TargetDBVersion] [/TD=TargetDBName][/TU=TargetUserName] [/TP=TargetUserPassword] [/MIGS = MigrationSequence] [/IMPS = ImportSystem] [/DIR = ExportDir] [/LOBDIR = LOBFilesDir] [/IMPDIR = ImportDir] [/IMPLOB = ImpLOBDir] [/OSN = OutSchemaName] [OTN = OutTableName] [/OFN = OutFilesName] [/OTF = OutTextFileName] [/EMPS] [/DDL] [/OF = OutFormat] [/CDEL = ColDel] [/LDEL = LineDel] [/DECPT = DecPoint] [/STDEL = StDel] [LOBIN] [/TABLST = ListFileName] [/R = RowsPrefetch] [/INI = IniFile] [/OPT = OptionsFile] [/NSTOP] [/GCMD = GenCmdFile] [/NODDL] [/NOCMD] [/LOG = LogFile] [/TRACE] [/REG = RegInfo] [/UNREG]

## Command Prompt Options

The command prompt parameters are not case sensitive and can be specified in any order.

- /D - Data source name (ODBC alias)
- /U - User name
- /P - Password
- /T - Table name, list or template (like *.*)
- /V - View name, list or template (like *.*)
- /SP - Stored procedure name, list or template (like *.*) - SQLWays Pro and Enterprise only
- /FN - Function name, list or template (like *.*) - SQLWays Pro and Enterprise only
- /TG - Trigger name, list or template (like *.*) - SQLWays Pro and Enterprise only
- /S - SQL SELECT statement
- /SF - File containing SQL SELECT statement
- /TF - File containing list of tables for converting
- /EXC - List of columns to be excluded from converting (default none)
- /SROW - Start row (default 1)
- /CNROWS - Number of rows to be exported (default all rows)
- /TARGET - Type of the target database (default none)
  - Oracle - Oracle database
  - DB2 - IBM DB2 database
  - MSSQL - Microsoft SQL Server database
  - Sybase - Sybase database
  - MySQL - MySQL database
  - Pervasive - Pervasive.SQL database
- /TVER - Target database version
- /TD - Target database name
- /TU - User name for the target database
- /TP - User password for the target database
- /MIGS - Migration sequence (default Clean)
  - Clean - Create constraints before importing data
  - Fast - Import data before creating constraints and indexes
  - Ready - Create constraints and indexes before importing data
- /IMPS - Import system (default Windows)
  - Windows - Microsoft Windows
  - Unix - Unix family
- /DIR - Directory for export files (default current)
- /LOBDIR - Directory for LOB files (default subdirectory LOBS of /DIR)
- /IMPDIR - Directory where import will be executed (default /DIR)
- /IMPLOB - Import directory for LOB files (default subdirectory LOBS of /IMPDIR)
- /OSN - Output schema (owner) name (default the source schema (owner) name)
- /OTN - Output table name (default name of the source table)
- /OFN - Output files name (default name of the output table)
- /OTF - Output text file name (possibly with an extension)
- /EMPS - Omit the schema (owner) name in the DDL statements
- /DDL - Generate DDL statements only
- /OF - Output format (default depends on /TARGET)
  - CSV - Column-delimited (CSV) output format
  - FIX - Fixed length output format
  - TAB - TAB-delimited output format
  - INS - SQL INSERT statements
  - XML - XML output format
  - BTR - Btrieve output format
- /CDEL - Column delimiter (default comma)
- /LDEL - Line delimiter (default carriage return and new line symbols)
- /DECPT - Decimal point character (default period)
- /STDEL - Statement termination string (default semicolon)
- /LOBIN - Write the LOB data inside the text file
- /TABLST - Generate list of tables available by using template /T
- /R - Prefetch count (default 1000)
- /INI - Initialization file (default sqlways.ini)
- /OPT - Options file (default use command prompt only)
- /NSTOP - Continue when an error occurs
- /GCMD - General command file name (default depends on /IMPS)
- /NODDL - Not generate DDL scripts
- /NOCMD - Not generate OS command files
- /LOG - Logging information file name (default sqlways.log)
- /TRACE - Run in trace mode
- /REG - Run for registration
- /UNREG - Run for unregistration

### /D - Data source name (ODBC alias)

Syntax: /D=DataSourceName

This option specifies the name of the database from which definitions and data are exported. This is an ODBC alias for the database.

This option allows the user to specify any data source type supported by ODBC: System, User or File DSN. For example, to specify a System or User DSN set /D=DsnName, to specify a File data source set /D=C:\PathToFileDSN\FileDsn.dsn.

This option is obligatory. If you work with one database all the time specify the database name in the SQLWays.ini file. Then when you omit this option in the command prompt its value is taken from the initialization file. See SQLWays.ini File Options for details.

### /U - User name

Syntax: /U=UserName

Specifies the name of the user who is connecting to the source database.

If you use the same login information all the time you can specify it in the SQLWays.ini file. In this case you can omit this information in the command prompt every time you run SQLWays. See SQLWays.ini File Options for details.

### /P - Password

Syntax: /P=Password

Specifies the password of the user who is connecting to the source database.

If you use the same login information all the time you can specify it in the SQLWays.ini file. In this case you can omit this information in the command prompt every time you run SQLWays. See SQLWays.ini File Options for details.

### /T - Table name, list or template

Syntax: /T=[SchemaName.]TableName [, NextTable]

This option specifies the tables that are exported.

If the database supports schemas (table owners) you can either specify a schema (owner) name for the table explicitly or use the default schema (owner) name for the user connected to the database.

You can provide a comma-separated list of tables or table templates. For example, /T=*.* or /T=%.% will export all tables accessible in the database, /T=schema1.*, schema2.* or /T=schema1.%, schema2.% will export all tables of the schemas schema1 and schema2.

Note: Some databases don't support the schemas. For example, to export all tables of an Access database you have to use /T=* or /T=%.

When this option is specified all rows and columns of each table are exported. You can define a subset of the table using options /EXC to exclude columns or /SROW and /CNROWS to specify the start row and number of rows. To define more complex subsets of the table or subsets based on queries or multiple tables use options for defining queries /S and /SF.

### /V - View name, list or template

Syntax: /V=[SchemaName.]ViewName [, NextView]

This option specifies the views whose definitions are extracted from the source database.

If the database supports schemas (object owners) you can either specify a schema (owner) name for the view explicitly or use the default schema (owner) name for the user connected to the database.

You can specify a comma-separated list of views or view templates. For example, /V=*.* or /V=%.% will extract all views accessible in the database, /V=schema1.*, schema2.* or /V=schema1.%, schema2.% will extract all views of the schemas schema1 and schema2.

### /SP - Stored procedure name, list or template

Syntax: /SP=[SchemaName.]StoredProcName [, NextStoredProc]

This option specifies stored procedures that are exported from the source database.

If the database supports schemas (object owners) you can either specify a schema (owner) name for the stored procedures explicitly or use the default schema (owner) name for the user connected to the database.

You can specify a comma-separated list of stored procedures or templates. For example, /SP=*.* or /SP=%.% will extract all stored procedures accessible in the database, /SP=schema1.*, schema2.* or /SP=schema1.%, schema2.% will extract all stored procedures of the schemas schema1 and schema2.

Note.This option is available in SQLWays Pro and Enterprise Editions only.

### /FN - Function name, list or template

Syntax: /FN=[SchemaName.]FunctionName [, NextFunction]

This option specifies functions that are exported from the source database.

If the database supports schemas (object owners) you can either specify a schema (owner) name for the functions explicitly or use the default schema (owner) name for the user connected to the database.

You can specify a comma-separated list of functions or templates. For example, /FN=*.* or /FN=%.% will extract all functions accessible in the database, /FN=schema1.*, schema2.* or /FN=schema1.%, schema2.% will extract all functions of the schemas schema1 and schema2.

Note.This option is available in SQLWays Pro and Enterprise Editions only.

### /TG - Trigger name, list or template

Syntax: /TG=[SchemaName.]TriggerName [, NextTrigger]

This option specifies triggers that are exported from the source database.

If the database supports schemas (object owners) you can either specify a schema (owner) name for the triggers explicitly or use the default schema (owner) name for the user connected to the database.

You can specify a comma-separated list of triggers or templates. For example, /TG=*.* or /TG=%.% will extract all triggers accessible in the database, /TG=schema1.*, schema2.* or /TG=schema1.%, schema2.% will extract all triggers of the schemas schema1 and schema2.

Note.This option is available in SQLWays Pro and Enterprise Editions only.

### /S - SELECT statement

Syntax: /S=SelectClause

This option specifies a SQL SELECT statement that defines the data to export.

You can use this option to export data based on a subset of the table, multiple tables or complex queries.

You can optionally enclose the statement in double quotes. If you need to exclude some columns from the table, consider using options /T and /EXC. If the statement is too large, consider using the option /SF that allows you to specify a file containing the statement.

### /SF - File containing SELECT statement

Syntax: /SF=Filename

This option specifies the file containing a SQL SELECT statement that defines the data to export. In all other respects, this option is the same as the /S option.

Filename may include the directory path to the file. The file can be located in any directory and may have any extension. You can use newline characters in SQL statements.

For example, /SF=emp.txt specifies the file from the current directory, /SF=d:\scripts\emp.txt specifies the file located in the d:\scripts directory.

### /TF - File containing list of tables for converting

Syntax: /TF=Filename

This option allows you to specify the file containing list of tables for converting. There can be only one table in each line of the file. To comment on a line use a semicolon in the first not blank position.

You can create a table list file manually or use the option /TABLST to generate it from the database by using templates.

If the file name is not explicitly specified the default file is sqlways.lst. The file must be located in the directory specified in the option /DIR.

### /EXC - List of columns to be excluded from converting

Syntax: /EXC=Column1 [,ColumnNext]

This option specifies a list of columns that must be excluded from converting. Columns must be separated by commas.

You can use the option /S to list the columns you want to convert. But in some cases especially when the column list is too long it is easier to list the columns you want to exclude. In this case it is recommended to use options /T and /EXC instead of /S.

### /SROW - Start row

Syntax: /SROW=StartRow

This option specifies the number of the start row to convert. The default value is 1.

If you want to use this option to split converting of a large table into parts, you should be careful, as in some cases it is not a safe way. If possible use SQL WHERE clause in the option /S to split a table.

### /CNROWS - Number of rows to be exported

Syntax: /CNROWS=CountOfRows

This option specifies the number of rows for exporting. The default value is all rows matching the query condition.

### /TARGET - Type of the target database

Syntax: /TARGET=TargetDBMS

This option specifies database type for generating database definition and import-load scripts.

Available values are:

- Oracle - Oracle database
- DB2 - IBM DB2 database
- MSSQL - Microsoft SQL Server database
- Sybase - Sybase database
- MySQL - MySQL database
- Pervasive - Pervasive.SQL database

If you use the same target database type all the time you can specify it in the SQLWays.ini file. See SQLWays.ini File Options for details.

If this option is not specified SQL and import-load scripts are not generated.

### /TVER - Target database version

Syntax: /TVER=TargetDatabaseVersion

This option specifies the version of the target database.

You can specify this option to adjust script generations for DDL statements and for importing data for particular version of the database.

The version option allows to define the features and options supported by the database. The default values are 9.0.1 for Oracle, 7.2 for IBM DB2, 2000 for Microsoft SQL Server, 12.5 for Sybase and 3.23 for MySQL.

You can specify an earlier version of the database, so that the features not supported by this version will not be used in the SQL and import scripts.

You can also specify the version of the target database in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /TD - Target database name

Syntax: /TD=TargetDatabaseName

This option specifies the name of the target database. For Oracle, this is the service name.

If specified, this value will be used in the generated command scripts for creating DDL statements and importing data.

You can also set the name of the target database in the corresponding database section of the SQLWays.ini file. See SQLWays.ini File Options for details.

### /TU - User name for the target database

Syntax: /TU=TargetUserName

This option specifies the user name for the target database.

If specified, this value will be used in the generated command scripts for creating DDL statements and importing data.

You can also set the user name for the target database in the corresponding database section of the SQLWays.ini file. See SQLWays.ini File Options for details.

### /TP - User password for the target database

Syntax: /TP=TargetUserPassword

This option specifies the password of the user for the target database.

If specified, this value will be used in the generated command scripts for creating DDL statements and importing data.

You can also set the user password for the target database in the corresponding database section of the SQLWays.ini file. See SQLWays.ini File Options for details.

### /MIGS - Migration sequence

Syntax: /MIGS=MigrationSequence

This option specifies the migration sequence for tables. Using this option you can choose the order of creating table constraints, importing data and creating indexes.

Available values are:

- Clean - Create constraints before importing data
- Fast - Import data before creating constraints and indexes
- Ready - Create constraints and indexes before importing data

Depending on this option SQLWays creates different command files to import tables.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /IMPS - Import system

Syntax: /IMPS=ImportSystem

This option specifies the system where import to the target database will be executed. SQLWays allows importing of database definitions and data on a Microsoft Windows or Unix system.

Possible values are Windows and Unix. The default value is Windows. When /IMPS=Windows is specified, SQLWays generates command files for importing using the Windows command interpreter. When /IMPS=Unix is specified, SQLWays generates Bourne shell scripts.

This option also defines rules for the path and new line delimiters that are used in the output scripts and files generated by SQLWays. Windows uses a backslash symbol as the directory delimiter (d:\temp\dir\subdir1) whereas Unix uses a slash symbol (tmp/dir1/subdir1). In Windows a new line is defined by carriage return and new line characters (0x0D0A or \r\n), while in Unix a new line is represented by new line character only (0x0A or \n).

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /DIR - Directory for export files

Syntax: /DIR=ExportDir

This option specifies the directory for export files. The default value is the current directory. SQLWays uses this directory to save export data files, SQL and import scripts and log files.

If the directory does not exist SQLWays creates it. You can set the directory in the SQLWays.ini file. See SQLWays.ini File Options for more information.

### /LOBDIR - Directory for LOB files

Syntax: /LOBDIR=LOBFilesDir

This option specifies the directory where files for LOB objects are created. The default value is the subdirectory \LOBS of the directory specified by the option /DIR.

For every LOB object one file is created and its path is specified in the text file.

LOB objects are CLOB and BLOB data types in Oracle, IBM DB2; TEXT and IMAGE data types in MS SQL Server, Sybase; and MEMO data types in Access, FoxPro.

### /IMPDIR - Directory where import will be executed

Syntax: /IMPDIR=ImportDir

This option specifies the directory where import will be executed. The default value is the export directory specified by the option DIR.

If you plan to move export files to other location to perform import, you have to specify the import directory in this option. Using this option SQLWays will properly generate import scripts that contain file references.

If you will execute import on a Unix system, you can specify Unix paths in this option, like /usr/reports/data/.

You can set the import directory in the SQLWays.ini file. See SQLWays.ini File Options for more information.

### /IMPLOB - Import directory for LOB files

Syntax: /IMPLOBDIR=ImportLOBDir

This option specifies the directory where LOB files for importing are located. The default value is the subdirectory \LOBS of the import directory specified by the option /IMPDIR.

If you plan to move export files to other location to perform import and LOB files are not located in the subdirectory LOBS of /IMPDIR, you have to specify the import directory for LOB files. This will allow SQLWays to generate properly import scripts that contain references to LOB files.

You can set the LOB import directory in the SQLWays.ini file. See SQLWays.ini File Options for more information.

### /OSN - Output schema (owner) name

Syntax: /OSN=OutSchemaName

This option allows you to change the schema (owner) name for database objects. If a value is specified, SQLWays changes the source schema (owner) name to the specified value. If no value is specified, the schema (owner) name is not changed and the source value is used.

If you want to omit the schema (owner) name in SQL scripts, use the option /EMPS. This allows you to use the default schema (owner) name for the user.

If you want to change both schema (owner) and table names, consider using the option /OTN.

### /OTN - Output table name

Syntax: /OTN=[OutSchemaName.]OutTableName

This option specifies the name of the output table. This table name is used in the DDL and import-load scripts. The default value is the name of the source table.

If you want to change only the schema (owner) name for the table, consider using the option /OSN.

### /OFN - Output files name

Syntax: /OFN=OutFilesName

This option specifies the name of the output files. The output files are text, log and scripts files. The default value is the name of the output table.

The file extensions like .txt, .sql, .cmd are added to this file name depending on the output file.

### /OTF - Output text file name

Syntax: /OTF=OutTextFileName

This option specifies the output file name and possibly a file extension for the text file. By default, the file name is selected from the table name or from the option /OFN and .txt file extension is added.

When this option is specified .txt file extension is not added and any other file extension can be specified.

### /EMPS - Omit the schema (owner) name in DDL statements

Syntax: /EMPS

This option specifies that schema (owner) names will be omitted in SQL scripts for DDL statements. This allows you to use the default schema (owner) name for the user.

When the target database is Pervasive.SQL, schema names are always omitted even if the /EMPS option is not specified since Pervasive.SQL does not support schemas (logical grouping of objects in the database).

If you want to change the schema (owner) name for database objects, consider using the option /OSN.

You can set this option in the [DDL] section of SQLWays.ini file. See SQLWays.ini File Options for more information.

### /DDL - Generate DDL statements only

Syntax: /DDL

This option specifies that only SQL scripts for database definitions (tables, indexes, primary keys, referential, check and unique constraints etc.) are generated. When this option is specified the data are not exported and import-load scripts are not generated.

### /OF - Output format

Syntax: /OF=OutFormat

This option specifies the output format for the text file.

Available values are:

- CSV - Column-delimited (CSV) output format
- FIX - Fixed length output format
- TAB - TAB-delimited output format
- INS - SQL INSERT statements
- XML - XML output format
- BTR - Btrieve output format

The default value depends on the /TARGET option. If the /TARGET is Oracle, DB2 or not specified the default value is CSV format. If the /TARGET is MSSQL, Sybase or MySQL the default value is TAB format. This format is recommended for moving data into MS SQL Server, Sybase and MySQL databases.

If the /TARGET is Pervasive, the default value is BTR. This is the Btrieve ASCII file format for the BUTIL utility that loads data into a Pervasive.SQL database.

### /CDEL - Column delimiter

Syntax: /CDEL=ColumnDelimiter

This option specifies a column delimiter for the text files. This option can be used for the CSV format only. The default value is a comma. It is possible to specify one or multiple characters as a column delimiter.

To specify the hexadecimal value of the delimiter use the following syntax: 0xhh. For example, /CDEL=0x2c specifies a comma as the column delimiter. Non printing characters like tab, carriage return and new line can be represented by \t, \r and \n accordingly. To specify a backslash character use \\.

You can combine different character representations to specify a column delimiter. For example, /CDEL=|||0x2c0x2c|||

Note. To use a TAB character as a column delimiter use the TAB output format.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /LDEL - Line delimiter

Syntax: /LDEL=LineDelimiter

This option specifies a line delimiter for the text files. The default value is carriage return and new line characters (0x0D0A or \r\n) unless /IMPS=Unix is specified. If /IMPS=Unix is specified the default value is new line character (0x0A or \n).

Using this option you can specify any string as a line delimiter. The nonprinting characters like tab, carriage return and new line can be represented by \t, \r and \n accordingly.

In most cases, if there are newline characters in the data, you have to change the default value to any other string that does not exist in the data. This will allow to process rows properly by import/load utilities.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /DECPT - Decimal point character

Syntax: /DECPT=DecPoint

This option specifies a single character which is used instead of a decimal point character for numeric values. The default value depends on Regional Settings.

To specify the hexadecimal value of a decimal point character use the following syntax: 0xhh. For example, /DECPT=0x2c specifies a comma as a decimal point character.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /STDEL - Statement termination string

Syntax: /STDEL=StatementDelimiter

This option specifies a string that is used to terminate SQL statements in scripts. The default value is a semicolon (;) unless the target database (/TARGET) is Sybase or Microsoft SQL Server. If the target database is Sybase or Microsoft SQL Server the default value is GO.

To specify the hexadecimal value of a character belonging to the statement delimiter, use the following syntax: 0xhh. For example, /STDEL=0x40 specifies the AT symbol (@) as the statement termination string.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for more information.

### /LOBIN - Write the LOB data inside the text file

Syntax: /LOBIN

This option specifies that the data of LOB columns (CLOB, BLOB, TEXT, IMAGE and MEMO) are written inside the text file.

By default the LOB data are written into separate files unless /TARGET is MSSQL, Sybase or MySQL. This allows the LOB data to be moved into Oracle and IBM DB2 using SQL Loader and DB2 IMPORT/LOAD utilities.

When /TARGET is MSSQL, Sybase or MySQL the LOB data are written inside the text file even if the /LOBIN option is not specified. This allows the LOB data to be moved into MS SQL Server and Sybase using the BCP utility and into MySQL using LOAD DATA INFILE command.

### /TABLST - Generate list of tables available by using template

Syntax: /TABLST=[FileName]

When this parameter is specified, SQLWays generates only the list of tables matching the template in the option /T into the file.

For example, the command SQLWays /t=dept.* /tablst=dept.lst will generate the list of tables belonging to the schema DEPT into the file dept.lst. Then you can comment tables that you don't want to convert (using a semicolon in the first line position) and run SQLWays /tf=dept.lst.

You can also use this parameter to see which tables are available on a data source.

If the file name is not explicitly specified the default file is sqlways.lst. The file is saved in the directory specified in the option /DIR.

### /R - Prefetch count

Syntax: /R=RowsPrefetch

This option specifies the number of rows that are read before they are saved in the output file. The default value is 1000 rows.

Also this value is used to specify internal buffers and commit points in generated scripts for supported import-load utilities. Specifying this option can significantly speed up data exporting and especially importing-loading.

### /INI - Initialization file

Syntax: /INI=InitializationFile

This option specifies the path and name of the initialization file that is used to save frequently used options and to adjust script generations. For more information about the structure and options of this file see SQLWays.ini file options.

By default, if the /INI option is not specified, SQLWays uses SQLWays.ini file. SQLWays searches for the file in the following sequence:

- The current directory.
- The directory from which the application loaded.

This option can be used to specify different initialization files to be used by SQLWays. This allows implementing various migration routines that involve various databases and their versions.

For example, if /ini=d:\ini\sqlways.ini is specified then the file sqlways1.ini from the directory d:\ini\ is used as the initialization file.

### /OPT - Options file

Syntax: /OPT=OptionsFile

This option specifies a file that contains additional command prompt options. You have to specify options in this file in the format as they are appeared in the command prompt.

The options file can not contain options of the initialization file SQLWays.ini. To specify different options of the initialization file, use the option /INI.

### /NSTOP - Continue when an error occurs

Syntax: /NSTOP

This option specifies to continue processing when an error occurs. If you specify this option and an error occurs SQLWays does not stop processing and tries to process the next table.

You can set this option in the SQLWays.ini file. See SQLWays.ini File Options for details.

### /GCMD - General command file name

Syntax: /GCMD=GenCmdFile

This option specifies the general command file that contains scripts for importing all exported database objects (tables, views etc).

SQLWays creates one command file for each exported object. This command file contains DDL statements and import/load scripts (for tables) for one object only. This allows to import each database object separately.

To simplify the transfer of large number of database objects, you can use the general command file that allows importing all objects at once. The tables in the general command file are ordered by referential constraints, the tables that are referenced by other tables imported at first.

The default general command file is sqlways_all.cmd (Windows batch file) if /IMPS=Windows is specified, and sqlways_all.sh (Bourne shell script) if /IMPS=Unix is specified.

The file is saved in the directory specified in the option /DIR.

If the option is not specified the general command file with the default name (see above) is created when the number of exported objects is greater than 1. If the option is specified the general command file is always created despite the number of exported objects.

### /NODDL - Not generate DDL scripts

Syntax: /NODDL

This option specifies that DDL scripts will not be created when exporting tables. This option can be used when the data are imported into existing tables.

When this option is not specified and the target database is defined SQLWays creates DDL scripts that can be used to recreate table definitions in a newly created database e.g.

### /NOCMD - Not generate OS command files

Syntax: /NOCMD

This option specifies that OS command files will not be created when exporting tables. SQLWays creates OS command files to invoke database utilities to execute DDL statements and to import data to the target database.

### /LOG - Logging information file name

Syntax: /LOG=LogFileName

This option specifies the log file that will be used to store logging information about the exporting process.

The default log file is sqlways.log. The file is saved in the directory specified in the option /DIR.

### /TRACE - Run in trace mode

Syntax: /TRACE

When this option is specified detailed information is written to the log file. This information is typically requested by the support and can help to solve database and other problems.

### /REG - Run for registration

Syntax: /REG=[RegName][;RegNumber]

Use this option to enter registration information. You should enter registration name and number. See license.txt file supplied together with install package for license agreement.

If you omit registration name and number in the command prompt, for example, running SQLWays.exe /REG or SQLWays.exe /REG=CompanyName, SQLWays asks you to enter missing information.

### /UNREG - Run for unregistration

Syntax: /UNREG

You can use this option to unregister SQLWays on the computer. See license.txt file supplied together with install package for license agreement.

[Main] [Table of Contents]
Copyright © 1999-2003 Ispirer Systems. All Rights Reserved.
SQLWays™ www.ispirer.com.