Does your ssis package ever miss data? It seems like sometimes it just misses pieces of information here and there…randomly.
I had this nagging problem: I would run my package and all of my data would update/insert fine except for one or two pieces. I would then dig through the code, procedures, etc…not find anything and finally run the package again on the file and it would work. All data would update/insert correctly.
I refused to
a.) believe that SSIS wasn’t processing everything
b.) build a job to run the file twice.
More specifically, my lookup didn’t seem to find stuff occasionally. Have you ever noticed that when you run your package some objects light up yellow before it finishes the previous operation?
Image may be NSFW.
Clik here to view.
This clued me in to the possibility that something was being prepared before I was ready for it to be prepared. It’s not in the picture, but my lookup was occurring at the same time as my insert so it was missing the new data because it was caching the data before I was ready for it to be cached.
So after reviewing this page I changed my lookups to ‘No Cache’ and never had the problem again. Setting it to no cache made it go back to the server to retrieve the data which enabled it to catch the new inserts. Because I was working with a small amount of data I wasn’t concerned with memory issues.
Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
