<div>
Good enough for me. I'll proceed to use Firstrow = 2 knowing I am in good company.
</div>


Good enough for me. I'll proceed to use Firstrow = 2 knowing I am in good company.

<div>
<div class="content wysiwyg-content">
My application needs to import data from .csv files created by an Agilent ICP-MS laboratory instrument running under MS Windows. It creates a consistent set of .csv file with column heading in the first row. I have created a table tblFromICPMSRaw with the same column names and each field defined as nvarchar(255), <br />
<br />
DELETE FROM &nbsp;[GSAData].[dbo].[tblFromIC<wbr />PMSRaw] <br />
BULK INSERT &nbsp;[GSAData].[dbo].[tblFromIC<wbr />PMSRaw] <br />
FROM &nbsp;'\\NATHONG\GSAJDrive\Instr<wbr />umentOutpu<wbr />tFiles\ICP<wbr />MS\New\182<wbr />023.csv'<br />
WITH (Codepage = 'ACP', Datafiletype = 'char', Fieldterminator = ',', Firstrow = 2)<br />
<br />
It works just fine, with me specifying FIRSTROW = 2 to not import the column headers (Row # 1)<br />
<br />
But I found this note in the Transact SQL definition of Bulk Insert<br />
&quot;&nbsp;Note: <br />
The FIRSTROW attribute is not intended to skip column headers. Skipping headers is not supported by the BULK INSERT statement. When skipping rows, the SQL Server Database Engine looks only at the field terminators, and does not validate the data in the fields of skipped rows. &quot;<br />
<br />
What, if any, risk am I running by ignoring this note?
</div>
</div>


My application needs to import data from .csv files created by an Agilent ICP-MS laboratory instrument running under MS Windows. It creates a consistent set of .csv file with column heading in the first row. I have created a table tblFromICPMSRaw with the same column names and each field defined as nvarchar(255), 

DELETE FROM  [GSAData].[dbo].[tblFromICPMSRaw] 
BULK INSERT  [GSAData].[dbo].[tblFromICPMSRaw] 
FROM  '\\NATHONG\GSAJDrive\InstrumentOutputFiles\ICPMS\New\182023.csv'
WITH (Codepage = 'ACP', Datafiletype = 'char', Fieldterminator = ',', Firstrow = 2)

It works just fine, with me specifying FIRSTROW = 2 to not import the column headers (Row # 1)

But I found this note in the Transact SQL definition of Bulk Insert
" Note: 
The FIRSTROW attribute is not intended to skip column headers. Skipping headers is not supported by the BULK INSERT statement. When skipping rows, the SQL Server Database Engine looks only at the field terminators, and does not validate the data in the fields of skipped rows. "

What, if any, risk am I running by ignoring this note?

Question about using BULK INSERT to import a .csv or .txt file

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.