Microsoft SQL Server bcp

This section lists the configuration file parameters that affect cloning with bcp, as well as the files that are created when you use bcp.

Note: You must select the Select Into/Bulk Copy option. Failure to select this option may result in a corrupt log device.

The following client configuration file parameters affect the bcp utility. For more details, see [Bulk_Loader].




The bcp utility can load a table in several batches instead of loading the entire table in a single operation. You can control the bcp utility batch size using this parameter.


Adds the -C code_page to the bcp command line. For example, because the Japanese code page is 932, setting this parameter to 932 adds -C 932 to the bcp command line.


Defines the network packet size value for the bcp utility (applies to remote servers only). If you have wide tables, setting this parameter to a packet size larger than the default (4096) can speed up loading the data into the table at the expense of system resources.


Defines the format in which the bcp expects dates. The dbutility program uses this information (which is only needed for non-US sites) to properly format dates that are passed to the bulk loader.


Enables the bcp_auditor program to determine whether or not a bcp was successful in cases where the database language is not English.


Preserves TAB characters in the data.


Controls the bulk loader’s tolerance to records that are discarded due to data errors.


Activates the segmented bulk load feature, which allows you to specify the maximum amount of storage that dbutility should use for temporary files.


This parameter works in the following ways:

  • Causes the bcp to assume that all data fields are type CHAR when the data is being loaded into the relational database
  • Forces the bcp to use the tab character as the bcp delimiter.