January 13, 2011 at 4:28 am
Hi
I've discovered an issue with the text qualifier field in the file connection manager when upgrading a SSIS 2005/2008 package from a 32 bit platform to 64 bit platform runninn SQL Server 2008 R2 10.5.1600.
The package will convert <none> in this field to _x003C_none_x003E and therefore any package using the file connection manager i.e. import/export - common tasks on SSIS! will cause problems either with output data or imported data.
Simply replacing _x003C_none_x003E with <none> fixes the issue but ofcourse there can be many packages affected as a result.
Does anyone know if there is an existing/impending cumulative update for SQL Server 2008 R2 Standard that will fix the problem?
N.B. double quote delimiters are converted to _x0022_ which I am assume by replacing with a double quote will fix the problem.
Thanks
Mark
April 19, 2011 at 2:23 pm
I am facing the same problem, are you able to get the resolution?
May 25, 2011 at 10:06 am
I am also experiencing this issue. I believe it's related to the Package Import Wizard that is used in both Integration Services and Visual Studio. In my instance, both my workstation and the database server are running Windows 7 64-bit. What I'm seeing is that my text qualifier is being changed from " to _x0022_ when I deploy a package to Integration Services, as well as in Visual Studio when I add an existing package to a project.
May 25, 2011 at 10:59 am
Unfortunately, found no fix at the time, so manually fixed all packages and has worked fine.
August 2, 2011 at 10:27 am
If you use package configurations on your packages you can add one for the "'\Package.Connections[<your_connection>].Properties[TextQualifier]" and set it "<none>". For whatever reason when it reads it from the configuration it interprets it correctly, but when it pulls it from the package it does not.
June 28, 2012 at 10:44 pm
Howdy
I was experiencing this problem as well - from dev workstation to Server (both different versions of SQL 2008 r2). Whilst the ideal development environment is to have everything at the same version/service pack/CU, this is not something I can control.
However, Gentile's solution to use SSIS configurations is a great workaround that works for my environment
...Thanks for that
January 8, 2015 at 8:12 am
I've seen a fix that looks promising... to populate the flat file configuration manager text delimiter to be:
'"'
That is, a double quote inside of single quotes.
*******************
What I lack in youth, I make up for in immaturity!
January 8, 2015 at 8:50 am
Yes - I think that's what i did and has been working well since, though I also think it may have been fixed in latest patches (I did a notepad++ compare of two dtsx files just yesterday and shows the change). Sorry not replied earlier to this post, I've had two children since the post..............
January 8, 2015 at 2:33 pm
Just deleting the garbage gets you going but does not prevent it from happening again. Supplying a default ends the issue.
Congratulations. Children are the best thing in life.
*******************
What I lack in youth, I make up for in immaturity!
February 24, 2015 at 6:08 pm
SQLServer2008-KB971490-x64.exe resolved the issue of "_x003C_none_x003E_" but "_x0022_" still persists. (sql server 2008 sp3).
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply