OK, I am not even sure I can explain this let alone know what is going on. SQL 2008 enterprise, 64 bit. We have a stored procedure (no changes between working and not working). Running this against the same server file folder, same security credentials, from the BI tool, is just fine. When run from a SQL server job, results as below. SSIS job basically execs this stored procedure, which just selects and formats the data. The SSIS package creates a CSV file on a Win. Server. All of a sudden (I know there is no all of a sudden) it creates this CSV file as such: _x003C_none_x003E_"MOORING"_x003C_none_x003E_,_x003C_none_x003E_"RANDY"_x003C_none_x003 Instead of as such: "MOORING","RANDY" I've tried a number of things, and like I said it works on my PC within the VS. Ideas on either fixing it or troubleshooting it?

All of a sudden (I know there is no all of a sudden) it creates this CSV file as such: What changed? It looks like the data is surrounded with a strange string in addition to " .Kalman Toth, SQL Server & Business Intelligence Training; SQL 2008 GRAND SLAM

We had an upgrade of the application the source of the data resides on (SQL server 2000 is the DB). When that was done I got a truncation error and needed to update the metadata. Since the application is a vendor supplied application, I guessed there was a table change since a few other things had the same issue. All I had to do was open the data flow (which contains a ODBC source and Flat File destination, nothing else), save, build and replace. That's when it started happening. But like I said, when I run it from my desktop from VS, it works just fine.

I would just create a brand new package. Let us know what happens.Kalman Toth, SQL Server & Business Intelligence Training; SQL 2008 GRAND SLAM

When I look up 3C and 3E in the ascii and UNICODE charts they are 3C = <, 3E = >. So therefore I am assuming the file is putting out <none>"MOORING"<none>,<none>"RANDY"<none> but because I am telling it it is ANSI (code page 1252 I think, going from memory) don't suppose that rings any bells?

OK, found the cause, and the fix. But it seems to be a bug on SQL 2008, maybe SR1. Once I realized the "garbage" was truly <none>, I went back and looked through EVERYTHING again. Guess what, I found that string <none> in the TEXT QUALIFIER setting of the flat file manager. Humm, I says to myself, that is interesting, since VS put that there. So I just wiped out the <none> in the properties, made sure it didn't put it back. Save, Build, deploy. Works OK now it appears.

Perfect, this fixed my problem as well... I had another issue that I was getting _x0022_ showing up as well and that was a Text Qualifier of " Strange behaviour for certain, but it is working now...

I just wanted to note that when I used the "Flat File Connection Manager Editor" to remove the <none> qualifier, VS added it back in. If instead I use the Properties Window to remove it the <none> stays gone, I am able to redeploy and successfully output my file. This appears to be an issue when the package was originally developed on an x86 box, and subsequently edited on an x64 box.

You just saved me from insanity!

See here for more info on why that weird behaviour is happening: http://sqlblog.com/blogs/jamie_thomson/archive/2010/11/25/sql-server-2008-sp1-cu-6-includes-small-changes-to-dtsx-files.aspx (Thank you Jamie!)

I also, found the answer to be in my values set for the flat file connection manager. Wipe out "none" as stated above and clear any value in the "text delimiter" Here is an article that has pictures: _x003C_none_x003E_ error LPlp

@Fo Fa, Thanks a bunch!!

You just saved me a lot of head scratching. Thank You! Thanks for your help