I have an SSIS job as follows:
I'm only looking against the ticketId in both source/destination.
The issue is that out of the 2288, many should be new rows which don't exist in the destination DB but it seems like they all go to the Update condition instead.
What can be the issue here?
You don't need the conditional. Just do the lookup redirecting the not-found tickets to added row count.
Yes it is looking at source TicketID, you would have to expose TickedID from lookup and then check this against NULL.
After that you need to change conditions to:
Also @Jayvee has a valid point that you can skip conditional split completely and redirect rows directly from lookup.
Conditions has to be specified clearly , this transformation is looking at all Ticketid's instead of a case statement. SO its writing all towards update
1) isnull(TicketID) != isnull(TicketID) -- record not exists
2) isnull(TicketID) == isnull(TicketID) -- Record exists
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.