Bumped by Community user
    Bumped by Community user
3 Added relevant tag
| link
    Tweeted twitter.com/StackDBAs/status/728220838600843268
2 deleted 21 characters in body; edited tags
source | link

I am attempting to extract a table to CSV using BCP from SQL Server 2014 and the size of the file once the data is extracted is actually larger than the size of the database itself.

One thing to note is that one of the fields in this table is an nvarchar(max) and could contain values that exceed 8000 chars.

I was just wondering if this was normal behavior when extracting this type of data to file, or whether there was some trick that I could use to shrink the file size without any data loss.

Thanks,

Nikhil

I am attempting to extract a table to CSV using BCP from SQL Server 2014 and the size of the file once the data is extracted is actually larger than the size of the database itself.

One thing to note is that one of the fields in this table is an nvarchar(max) and could contain values that exceed 8000 chars.

I was just wondering if this was normal behavior when extracting this type of data to file, or whether there was some trick that I could use to shrink the file size without any data loss.

Thanks,

Nikhil

I am attempting to extract a table to CSV using BCP from SQL Server 2014 and the size of the file once the data is extracted is actually larger than the size of the database itself.

One thing to note is that one of the fields in this table is an nvarchar(max) and could contain values that exceed 8000 chars.

I was just wondering if this was normal behavior when extracting this type of data to file, or whether there was some trick that I could use to shrink the file size without any data loss.

1
source | link

File size when extracting from SQL Server to CSV

I am attempting to extract a table to CSV using BCP from SQL Server 2014 and the size of the file once the data is extracted is actually larger than the size of the database itself.

One thing to note is that one of the fields in this table is an nvarchar(max) and could contain values that exceed 8000 chars.

I was just wondering if this was normal behavior when extracting this type of data to file, or whether there was some trick that I could use to shrink the file size without any data loss.

Thanks,

Nikhil