Using Native, Character, or Unicode Formats
This section discusses the data formats that are supported for the bulk export or bulk import of data. Microsoft SQL Server can accept data in character or native binary format. Use character format when you move data between SQL Server and another application (such as Microsoft Excel) or another database server (such as Oracle or SQL Server). You can use native format only when you transfer data between instances of SQL Server.
Choosing a Data Format
The following table provides general guidelines for choosing a data format depending on how the data is represented and the source or target of the operation.
Operation |
Native |
Unicode native |
Character |
Unicode character |
|---|---|---|---|---|
Bulk transfers of data between multiple instances of SQL Server by using a data file that does not contain any extended or double-byte character set (DBCS) characters. Unless a format file is used, these tables must be identically defined. |
Yes1 |
— |
— |
— |
For sql_variant columns, use of native data format is best, because native data format preserves the metadata for each sql_variant value, unlike character or Unicode formats. |
Yes |
— |
— |
— |
Bulk transfers of data between multiple instances of SQL Server by using a data file that contains extended or DBCS characters. |
— |
Yes |
— |
— |
Bulk import of data from a text file that is generated by another program. |
— |
— |
Yes |
— |
Bulk export of data to a text file that is to be used in another program. |
— |
— |
Yes |
— |
Bulk transfers of data between multiple instances of SQL Server by using a data file that contains Unicode data and does not contain any extended or DBCS characters. See Using Unicode Character Format to Import or Export Data. |
— |
— |
— |
Yes |
1 Fastest method for the bulk export of data from SQL Server when using bcp.