July 3, 2014 at 1:04 pm
I'm hoping someone can help me. I have a big query, like 2 million records. It has some exotic characters, and I think some of the values have commas which is making it difficult to export the query results to a flat file and then import them into another table in a different server and database.
I've been trying to use the export wizard so I can change the column delimiter to tab, but I'm getting the errors below I think because of the exotic characters and merged values.
Any tips are greatly appreciated.
Errors:
Error 0xc02020a1: Data Flow Task 1: Data conversion failed. The data conversion for column "ACCOUNT_NM" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
(SQL Server Import and Export Wizard)
Error 0xc02020a0: Data Flow Task 1: Cannot copy or convert flat file data for column "ACCOUNT_NM".
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task 1: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - TestExport_txt" (172) failed with error code 0xC02020A0 while processing input "Flat File Destination Input" (173). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)
Error 0xc02020c4: Data Flow Task 1: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
(SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - Query" (1) returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)
July 3, 2014 at 2:15 pm
I would take a look at the BCP utility.
If you use -c it will convert everything to a char type and use a tab as a separator so you don't have to worry about embedded commas in your data. If you use -C RAW, it won't try to convert your exotic characters.
Typical command would look like
bcp "Query to run" myfile.dat -T -c -C RAW -S ServerName
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply