<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server Newbies
»
Running SSIS fails on local server, not...
Running SSIS fails on local server, not remotely
Rate Topic
Display Mode
Topic Options
Author
Message
Chi Chi Cabron
Chi Chi Cabron
Posted Thursday, July 05, 2012 2:22 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 09, 2013 3:20 PM
Points: 27,
Visits: 144
I have a
very
simple SQL Server 2008 R2 SSIS package that imports 4 .csv files into a table.
If I deploy the SSIS package to the remote SQL server and run it interactively from SSMS on my client machine, the package runs fine.
If I run that exact same SSIS package from SSMS on the actual SQL server, it fails with data conversion errors "Output Column [ColumnName] failed because truncation would occur...." on all columns in the .csv file. Scheduling the SSIS package raises the same data conversion errors.
I am logged in as the same user on both machines, and the location of the .csv files is the same (on the SQL server).
Does anyone know of something that would cause a single SSIS package to fail when executed locally on the SQL server, but NOT when executed remotely? I could have expected permissions errors, but data conversion errors? Any help would be appreciated!
Post #1325717
Rick Krueger
Rick Krueger
Posted Thursday, July 05, 2012 10:43 PM
SSC Veteran
Group: General Forum Members
Last Login: Yesterday @ 8:50 AM
Points: 262,
Visits: 576
I've seen that error when the text qualifier gets modified. Check out this blog
post
from @JamieT.
Rick Krueger
Follow
@dataogre
Post #1325838
rhythmk
rhythmk
Posted Friday, July 06, 2012 1:14 AM
Old Hand
Group: General Forum Members
Last Login: Saturday, November 10, 2012 9:30 AM
Points: 388,
Visits: 603
Chi Chi Cabron (7/5/2012)
I have a
very
simple SQL Server 2008 R2 SSIS package that imports 4 .csv files into a table.
If I deploy the SSIS package to the remote SQL server and run it interactively from SSMS on my client machine, the package runs fine.
If I run that exact same SSIS package from SSMS on the actual SQL server, it fails with data conversion errors "Output Column [ColumnName] failed because truncation would occur...." on all columns in the .csv file. Scheduling the SSIS package raises the same data conversion errors.
I am logged in as the same user on both machines, and the location of the .csv files is the same (on the SQL server).
Does anyone know of something that would cause a single SSIS package to fail when executed locally on the SQL server, but NOT when executed remotely? I could have expected permissions errors, but data conversion errors? Any help would be appreciated!
In both cases destination database and table remain same ?
--rhythmk
------------------------------------------------------------------
To post your question use below link
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Post #1325876
Chi Chi Cabron
Chi Chi Cabron
Posted Friday, July 06, 2012 10:54 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 09, 2013 3:20 PM
Points: 27,
Visits: 144
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog
post
from @JamieT.
That did it, thanks!
Post #1326215
rhythmk
rhythmk
Posted Monday, July 09, 2012 12:17 AM
Old Hand
Group: General Forum Members
Last Login: Saturday, November 10, 2012 9:30 AM
Points: 388,
Visits: 603
Chi Chi Cabron (7/6/2012)
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog
post
from @JamieT.
That did it, thanks!
Great !! But could you please post your findings and solution.
--rhythmk
------------------------------------------------------------------
To post your question use below link
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Post #1326666
Chi Chi Cabron
Chi Chi Cabron
Posted Monday, July 09, 2012 9:37 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 09, 2013 3:20 PM
Points: 27,
Visits: 144
rhythmk (7/9/2012)
Chi Chi Cabron (7/6/2012)
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog
post
from @JamieT.
That did it, thanks!
Great !! But could you please post your findings and solution.
I went to the post at http://sqlblog.com/blogs/jamie_thomson/archive/2010/11/25/sql-server-2008-sp1-cu-6-includes-small-changes-to-dtsx-files.aspx
This article states that the text qualifier property in the dtsx file pre-CU6 is read as ' " ' (double quotes), but post-CU6 it is read as "_x0022_".
Examples from the article:
Pre-CU6: <DTS:Property DTS:Name="TextQualifier" xml:space="preserve">"</DTS:Property>
Post-CU6: <DTS:Property DTS:Name="TextQualifier" xml:space="preserve">_x0022_</DTS:Property>
I checked the dtsx file I was running and, sure enough, the text qualifier character was "_x0022_". Checked the version of SQL Server on my local machine and it was completely up to date. Checked the version on the remote server and it was at CU 4 (d'oh!). So the server didn't know how to interpret the "_x0022_" text qualifier and was failing, but my client, being up-to-date, interpreted it correctly and worked. Or at least that's my interpretation.
Changing the text qualifier to " (double quotes) in the dtsx package allowed it to run on the server (CU4), but it would fail when I tried to run from my local client.
So I updated the SQL server (which should have been done, anyway) and now everything works as it should.
Like the blog post says:
There is of course a simple but important lesson here – make sure your developer workstations are running the same builds as your DEV, Test, UAT and Production boxes. Its the sort of problem that you should only encounter once because you’ll never make this stupid mistake twice. Right?
Post #1326931
boriskey
boriskey
Posted Monday, August 27, 2012 3:42 PM
Grasshopper
Group: General Forum Members
Last Login: Yesterday @ 5:59 AM
Points: 18,
Visits: 180
wow i could never guess that could be the issue! it helped me, thanks for sharing the link!
Post #1350626
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
