Hi, Thanks. I have followed the approach and it works fine now. 🙂

Hi, It was a simple oversight. When I had created a Flatfile connection, I had set the file as "Fixed Width" instead of "Delimited". Now this is resolved.

Thanks to...

I tried to export that to another table in the database with OLEDB destination and the complete data was exported. the column had 137000 characters....

Should i check something in the...

I have checked now and the size is 31947 characters in the file and the size is 32KB if those numbers make any sense...

Thanks,

Sudarsan

Yes, from advanced property

In the Data Source, Output is set to DT_Text and in the FlatFile destination, the input is DT_Text

Hi SteveB,

The datatype is set as DT_Text, but still I face the same situation.

Thanks,

Sudarsan

Thank you Gail Shaw

Lyn Pettis, Thanks for your response. But the 10 GB size was reached over a period of time say few years. So i dont expect that to grow immediately. Again...

Apparently this got fixed with a SQL server restart...

This problem surfaced as soon as we ran sp_updatestats. Now is there any link with this?

Yes, by default we will commit which is available in the BEGIN TRY...END TRY block...

ROLLBACK in CATCH block... but this is within the stored procedure which is called n number...

Nice effort, and thanks for sharing it across.

I want that in the backend..

Thanks a lot