bart.de.koning (9/1/2014)
good Article,I do not think the WMI Event handler is very reliable. I had it working for a remote UNC Fileshare but it often stopped listening without a reason. There are suggestions that there are limits to the amount of messages it can digest without a server reboot. Ultimately I replaced it in my package with a script task that uses System.IO and queries for File arrival with a timer.
Thanks.
I have heard reports of the WMI technique being a bit inconsistent at times. I think a lot of the overall performance level will depend on the environment, e.g. host OS, network quality, etc.
I did three articles on this topic, this one leveraging WMI directly being the first, and each building on the last. Here is the third one. At the end of the article I contrast the three techniques:
Using the Script Task in SSIS to Process Data Files When They Arrive[/url]
I have heard reports of even the FileSystemWatcher (used in the article above) behaving inconsistently when it comes to watching an SMB-NAS directory for a file. I have a mind to write a fourth article that implements a Script Task containing a simple for-loop with a check for a file, a Thread.Sleep and some logic around the timeout settings but I am not sure when, if ever, I will get around to writing it.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato