This article discusses the behavior of the BCP utility when extracting data from SQL Server tables to files and more specifically to CSV files.
Imagine that you have the below table:
As you can see, records 2 and 3 contain null values.
Then you export the table contents to CSV using BPC:
bcp "SELECT [code],[description],[price] FROM [TestDB1].[dbo].[product]" queryout "c:\tmptestExtract.csv" -c -C 1253 -t ; -S ".SQL2K14" -T
Example: Output 1
As you can see on the above screenshot, the output seems correct. The records’ NULL values have been replaced with empty strings.
Now consider that the original table, instead of NULL values has empty strings:
Let’s try again to export the new table contents to CSV using BPC:
bcp "SELECT [code],[description],[price] FROM [TestDB1].[dbo].[product]" queryout "c:tmptestExtract.csv" -c -C 1253 -t ; -S ".SQL2K14" -T
Example: Output 2
As you can see, the empty strings have been replaced by NULLs which correspond to the hexadecimal character x00.
Remarks and Conclusion
From the MSDN Library article on BCP, we read the following:
- out copies from the database table or view to a file. If you specify an existing file, the file is overwritten. When extracting data, note that the bcp utility represents an empty string as a null and a null string as an empty string.
Now, if you are going to feed the CSV file to another application for parsing and processing it, if the application does not explicitly handle possible occurrences of the NULL character then most probably an error will be occurred.