July 31, 2012 at 3:39 am
I am relatively new to ssis although i am getting better 🙂
I seem to struggle with lookups tho, a lot of the time i get the "lookup doesnt yeild a match" error when i am pretty sure it does
is this because i am not giving both match and no match outputs?
July 31, 2012 at 1:41 pm
erics44 (7/31/2012)
I am relatively new to ssis although i am getting better 🙂I seem to struggle with lookups tho, a lot of the time i get the "lookup doesnt yeild a match" error when i am pretty sure it does
is this because i am not giving both match and no match outputs?
I would say no. The outputs should have no impact on "matchedness."
when you have records that didn't match, but you feel that they should, use the data viewer to trap the exact info coming down the flow. You may find that you need to trim strings or convert numbers, etc., in order for a true match to occur.
July 31, 2012 at 3:15 pm
I agree that you should pay attention to leading and trailing spaces, in particular trim all of your text type columns. Where SQL Server will usually ignore those spaces, SSIS is basically a .Net product and much pickier about these sorts of things. I make it a rule to trim pretty much all text data regardless of source, and that would include trimming the query that loads your lookup as well.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply