Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


ssis do you need a path for both lookup outputs?


ssis do you need a path for both lookup outputs?

Author
Message
erics44
erics44
Old Hand
Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)

Group: General Forum Members
Points: 366 Visits: 739
I am relatively new to ssis although i am getting better Smile

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?
herladygeekedness
herladygeekedness
Old Hand
Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)Old Hand (318 reputation)

Group: General Forum Members
Points: 318 Visits: 813
erics44 (7/31/2012)
I am relatively new to ssis although i am getting better Smile

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.
Daniel Bowlin
Daniel Bowlin
SSCrazy
SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)

Group: General Forum Members
Points: 2954 Visits: 2629
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search