you can't - googling show you lots of threads on that and the answer is always the same.

depending on what you are trying to accomplish there are ways to bypass...

AV blocking powershell

Access to that networkshare not set correctly (both to the location of the csv file and to the PS script itself.)

you can check it by using a using...

reason why you got "double quotes" is because you set the field quote to an empty string - try the basic import

e.g. remove the following 2 options

, FIELDQUOTE = ''

,...

first - while you mentioned you had "memory errors" the errors you supplied had nothing to do with memory, but only with a file format error when using the bulk...

yes. a standard pattern for this...

whenever I see these errors on BCP its one of the following

• invalid CSV file - e.g. not Double quoted on "fields" that contains double quotes or CR or LF

...

have a look at the code below.

basically I've created a temp table (on your case it would be a Permanente one) staging table to load the raw data

these types of...

replace the strings and values with others - as long as the position and sizes are the same it will do - without it not much we can tell.

but regardless...

a text file would never look like that - that has formatting that would not be possible on a text file so you are showing us potentially a rendering of...

Also, if the %of duplicates is higher than the % of singles, then it may be better to copy the singles into a new table and switch out...

have you read the manual?

you already have the sql to execute - you just need to copy and paste the 2 lines and reduce the size accordingly yourself

you were given options and directions on your prior post - what did you do with it and if you did try it what was the result?

https://www.sqlservercentral.com/forums/topic/shrinkfile-option-not-working

and shrinkdatabase is not...

that is a SQL issue - not VS or Schema compare issue.

basically server needs more memory or needs to have less memory allocated to SQL Server - other processes running...

WOW, Frederico, YYY999 as variable names. Yes, at least "VSC" did make sense, given that we worked with a data that was called "Voucher Service Code". The naming convention...