freebcp man page
freebcp — bulk loading utility for Sybase and Microsoft databases
|freebcp|| [[⟨ |
freebcp is a utility program distributed with FreeTDS. freebcp replicates (in part at least) the functionality of the bcp utility programs distributed by Sybase and Microsoft. freebcp makes use of the DB-Library bcp API provided by FreeTDS. This API is also available to application developers.
The manual pages or online help for Sybase or SQL Server can be referenced for more detailed information on bcp functionality.
Tables and Files
- The name of the database containing object to be copied. Optional if the table/view is in the default database for
- The schema of the object being copied. If not provided, the default schema for
- The name of the database object you wish to access, typically a table. It can also be a view. All views can be read; some can be written, subject to constraints. With
objectcan also be an SQL query.
- Copy data from a host file to a database table.
- Copy data from a database table to a host file.
- indicates that
table_nameis in fact SQL, rather than a database object. freebcp will execute the query and write the results to a file. (It is a good idea to have the query return one and only one result set.)
- The name of an operating system file.
- Set the size of a TDS packet to packet_size. Not sure why you would want to do this, except as an experiment.
- The name of the default database to use. Overrides default database associated with the login account. Causes freebcp to issue a
dbnamecommand immediately after logging in, before commencing BCP operations.
- Write the data in datafile to the table's IDENTITY column. Without this flag, the identity data present in the datafile will be ignored, and new IDENTITY values will be generated for the imported rows.
- The first row to copy from the input file or database table. The default is the first row, row 1.
- The name and location of the
interfacesfile to search when connecting to servername. Overrides
- The last row to copy from an input file or database table. The default is the last row.
- SQL text to set connection options prior to the bcp operation. If
optionsis a valid filename, the SQL is read from the file instead. Sometimes needed for
-O `SET QUOTED_IDENTIFIER ON'.
- The password associated with
- The name of the Database Server to which to connect.
- For text or image columns, set the maximum number of characters to request from the server. Defaults to the setting in
freetds.conf. If not specified anywhere, defaults to the full size of the data.
- A database login name. For TDS 7+ connections, a domain login is attempted if
usernameis not provided.
- The number of rows per batch of data copied. Batching applies only when you are bulk copying into the database. Each batch of data is effectively “committed” into the database. The default value for
- The host data file is (or will be) in "character" format, i.e., a text file. Encoding is determined by the client charset attribute in
- Turn off any logging. (Unintuitive, perhaps.)
- Write errors to
errfile. For uploads. Includes line and column information, and the row data.
- The format of the host data file is described by
formatfile. The layout of
formatfileis identical to that understood by the Sybase and Microsoft bcp utilities, but is too complicated to describe here.
- Set bcp hints. For valid values, cf. bcp_options() in the FreeTDS Reference Manual.
- Stop after encountering
maxerrorerrors. Default 10.
- The host data file is in “native” format. This is a format that freebcp will be able to process, but is not portable or readable.
- The row terminator for a character file. May be more than one character. Default is newline ('\n'). Cf. -c, above.
- The field terminator for character file. Also known as a column delimiter. May be more than one character. Default is tab ('\t'). Cf. -c, above.
- Print the version information and exit.
- Read input data from file specified.
- Write output data to file specified.
- Specify character set to use to talk to server.
When connecting to a Sybase database server, it is required that the TDS 5.0 protocol be used. When connecting to a Microsoft SQL Server 2000 database server, the TDS 7 (or later) protocol is required.
Sybase and Microsoft define different versions of the bcp portion of TDS 4.2. Because FreeTDS has no way of knowing which type of server it's connected to, freebcp does not support version 4.2 of the TDS protocol.
freebcp first appeared in FreeTDS 0.60
The freebcp utility was written by⟨firstname.lastname@example.org⟩
Currently, there is no support for text data types in freebcp, when SQL Server 2000 is the target server.