May 2, 2012 at 8:14 am
Hi Everyone,
Hope all is well.
I have noticed an issue last night. One of the SSIS packages that outputs to a flatfile is appending a weird string which is "_x003C_none_x003E_" before and after the actual output in the flat file. AFAIK nothing has changed in the package ever since the package was created. But when I checked the connection manager of the flat file it appears that the name of each column that is specified has this string appended before and after the name of each column. I dont know why it is that way and how it got changed but when I changed the column names back to normal the package returns the expected output without any weird strings.
Did anyone face this kind of issue and know why this is happening? what was your fix?
Thanks a bunch.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 2, 2012 at 8:22 am
May 2, 2012 at 8:30 am
Thanks Peter, in my case the text qualifier was empty. But as I mentioned the strings got appended to the column names before and after in the advanced properties window of the flat file connection manager settings. Hence the output file was messed up. The package never returned such errors before except for last night. Its working fine now after I deleted those weird strings.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 2, 2012 at 8:40 am
this is a bug, if you are in fact using SQL2008R2 it was fixed in I think CU4 else it is definitely fixed in SP1. there must also be a fix for SQL2008 as well but dont know at what patch level.
This was the workaround our devs used:
There are 2 ways to edit the TextQualifier property of a flat file connection. One is to use an edit box and the other is to directly edit the property in the Property explorer. If you use the edit box and blank out the Text Qualifier then it actually sets the property to <none> (whether you want it to or not). If however you blank out the TextQualifier property directly in the Property explorer then it stays as blank.
---------------------------------------------------------------------
May 2, 2012 at 8:46 am
Thanks George. The version of sql is SS 2008 R2 SE.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 2, 2012 at 8:50 am
presuming you haven't already you should apply SP1, rolling out through dev and test first.
---------------------------------------------------------------------
May 2, 2012 at 8:57 am
I have applied SP1:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 2, 2012 at 9:28 am
sorry, SP1 for SQL, 10.50.1600 is RTM, applying SP1 will bring you up to 10.50.2500
the service pack 1 referred to in your post is for the windows OS.
---------------------------------------------------------------------
May 2, 2012 at 9:34 am
Thanks george...I will apply the patch on the my test, dev and staging before moving to production.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply