February 9, 2011 at 11:28 am
Is the Department field in the pipeline mapped to a destination column?
CEWII
February 9, 2011 at 11:38 am
yes it definitely is mapped correctly. i even deleted the OLE Destination and recreated it to make sure SSIS hadn't "forgotten" to update something. it's also coming through just fine in the data viewer. the only thing remarkable about this problem field is that it's foreign keyed against another table but i also have other fields in this same data flow that are foreign keyed that are updating just fine.
February 9, 2011 at 12:15 pm
I had to ask.. You wouldn't believe the number of times that it was that simple.
You might add a row counter after the destination and connect the error output then add a data-viewer there.. See if any errors are getting kicked out. You also might see if you can trace the connection.
I have to admit that short of a bad mapping I haven't seen it drop columns that ARE mapped. I have seen it redirect them to the error output because of bad foreign keys..
CEWII
February 9, 2011 at 12:28 pm
nope, no records being kicked past the destination. no errors or anything at all.
how would one go about tracing the connection as you mentioned? it's just driving me crazy because i can see all the data come through the viewer that i have just in front of the destination. it's just not putting the values in the table.
February 9, 2011 at 12:34 pm
I'm wondering if you might not be patched..
Please see this URL http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e0954385-b96a-46db-ab03-7c4c803e8d1d
It seems to be similar.
CEWII
February 9, 2011 at 1:11 pm
i think i'm on at least SP3 but am downloading SP5 to make sure i have all the hotfixes to date. will let you know how that goes.
Viewing 6 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply