Specifies that identity value or values in the imported data file are to be used for the identity column. For more information, see CREATE EXTERNAL DATA SOURCE. The external data source must be created using the TYPE = BLOB_STORAGE option added in SQL Server 2017 (14.x). Specifies a named external data source pointing to the Azure Blob Storage location of the format file that will define the schema of imported data.

FORMATFILE_DATA_SOURCE = ' data_source_name' If FIRE_TRIGGERS isn't specified, no insert triggers execute. If triggers are defined for INSERT operations on the target table, they're fired for every completed batch. Specifies that any insert triggers defined on the destination table execute during the bulk-import operation. If you choose to skip rows, the SQL Server Database Engine looks only at the field terminators, and doesn't validate the data in the fields of skipped rows. Skipping headers isn't supported by the BULK INSERT statement. The FIRSTROW attribute isn't intended to skip column headers. The default is the first row in the specified data file. Specifies the number of the first row to load. Specifies a named external data source pointing to the Azure Blob Storage location of the error file that will contain errors found during the import. ERRORFILE_DATA_SOURCE = ' errorfile_data_source_name' As soon as the errors have been corrected, the data can be loaded.Д«eginning with SQL Server 2017 (14.x), the error_file_path can be in Azure Blob Storage. ERROR.txt is created, which references each row in the error file and provides error diagnostics. Additionally, a control file that has the extension. An error occurs if the file already exists. The error file is created when the command is executed. These rows are copied into this error file from the data file 'as is.'

Specifies the file used to collect rows that have formatting errors and can't be converted to an OLE DB rowset. For an example, see Import data from a file in Azure Blob Storage. Specifies a named external data source pointing to the Azure Blob Storage location of the file that will be imported. If the data file contains ANSI extended characters, specify widenative.ДЇor more information, see Use Unicode Native Format to Import or Export Data (SQL Server).ДЄpplies to: SQL Server 2017 (14.x) and Azure SQL Database.

The widenative value offers a higher performance alternative to widechar. Create the widenative data file by bulk importing data from SQL Server using the bcp utility. Native (database) data types, except in char, varchar, and text columns, in which data is stored as Unicode. Native format is recommended when you bulk transfer data between multiple instances of SQL Server using a data file that doesn't contain any extended/double-byte character set (DBCS) characters.ДЇor more information, see Use Native Format to Import or Export Data (SQL Server).ДЇor more information, see Use Unicode Character Format to Import or Export Data (SQL Server). The native value offers a higher performance alternative to the char value. Create the native data file by bulk importing data from SQL Server using the bcp utility.

DATAFILETYPE valueДЇor more information, see Use Character Format to Import or Export Data (SQL Server). Specifies that BULK INSERT performs the import operation using the specified data-file type value. Transact-SQL Syntax Conventions Syntax BULK INSERT Imports a data file into a database table or view in a user-specified format in SQL Server Applies to: SQL Server (all supported versions) Azure SQL Database

Bulk filename string replacer