So to work round this problem, I have been looking at a script task to take entire lines from the CSV file and parse out the fields using a method described in 22.I also set the SQL job to run in 32-bit mode, but still the same results. Is it possible this is to do with component versions? I am running Visual Studio 9.1 SP. This is not a permissions problem as both jobs run successfully,īut the results are different between them. But what's baffling me is why the processing difference between Visual Studio and SQL Server initiated SSIS jobs. Over time, I have had various problems importing CSVs with SSIS.
In other words, the server has ignored the double-quotes as text qualifiers in the import file and where it has come across a comma in a text qualified field, it has taken that to be a field delimiter, and split the data accordingly even though it should "AB", "Abacus, Counting Instruments", "20 Number Way" "AA", "Acme, Manufacturing Company", "1 Main Street" In order to discover what was going on, I set the data flow task to ignore truncation errors on all imported fields. Now I am getting the results: The results are as expected, and everything is fine.īut since I deployed the job to SQL Server, I started getting truncation errors. When I run the job from Studio, I get the following results into the Names table:ĪA, Acme, Manufacturing Company,1 Main Street, Main SquareĪB, Abacus, Counting Intruments,20 Number Way, Counstville I have used Visual Studio to create a SSIS job with a Flat File connection. "AB","Abacus, Counting Instruments","20 Number Way","Counstville"
"AA","Acme, Manufacturing Company","1 Main Street","Main Square" I have a file which contains a list of names and identfiers that I want to import into a table called Names I am having an SSIS flat file import problem.
0 kommentar(er)
