December 11, 2014 at 2:21 pm
This is the issue:
I copied a package to create a new package with another import that had almost same layout.
Source file was using its path from an expression including the folder path from Configuration table.
I set the new path in the config table and execute the import. It was importing portion of files and not the entire file.
I worked on all mappings to make sure nothing is missing and because the source file had the exact format, nothing looked suspicious.
After more than 2 hours, I removed the source file connection and created a new connection to new path.
Obviously, it worked. As a rule of thumb, if SSIS acts weird, remove and recreate before spending quite time to do logical approaches!! Like reboot Windows OS as the first remedy.
I could not find any hint online, so I thought it may save some time for others.
Fred Esmaeili
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply