March 6, 2009 at 8:13 am
Hi group,
We have a ssis package which takes the flat files -> applies some business logic -> pushes to a destination table.
Currently there is a filewatcher on the share which kicks the SSIS package, when there is a new file found in the share. The flatfile name is supplied through the variable to the ssis package and the source connection is configured dynamically in runtime, the destination will too.
I would like to know is there any limitations or pitfalls with invoking the same package by multiple instances in parallel?
The destination table will not be the same, at any point of time, even if multiple instances of the ssis package are running.
Thanks,
Narasimha
March 9, 2009 at 6:42 am
The biggest issue will be performance. SSIS is a memory hog and each instance of the package (if it even allows you to kick off the package multiple times at the same time) will sap the server's memory at an exponetial rate.
Why did you design the package to be kicked off this way anyway? You could have used a FOR...EACH loop to pick up each of the files and then just scheduled the package job to run every five minutes. It would be a lot cleaner performance-wise and if there are no files to pick up, then the package doesn't actual execute.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply