> Hello Allan,
>
> If say, I receive only 3-4 files to process per day from those folders
> at any point of time in a day then will keeping my SSIS packages
> running continously monitoring these folders a resources intensive
> job?
>
> Will keeping SSIS packages running 24x7 cause any memory leaks? will
> they block much memory etc are my concerns behind avoiding them
> running 24x7.
>
> What you think will I face above problems if I keep SSIS Packages
> running 24x7?
>
> What Say?
>
> Thanks,
> Sachin R. Chavan.
> "Allan Mitchell" wrote:
>
>> Hello Sachin,
>>
>> If you do not want the package executing all the time watching then
>> you have restricted your choices. If you only wanted to watch for
>> one file and exit when that file dropped I would advocate
>>
>> http://www.sqlis.com/23.aspx
>>
>> If you want to watch for n files then I certainly would be looking at
>> a windows service coupled with the FileSystemWatcher class to fire a
>> package when the file drops
>>
>> --
>>
>> Allan Mitchell
>> http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com
>> |
>> http://www.konesans.com
>>> Hi,
>>>
>>> I need your thoughts on how to accomplish following task:
>>>
>>> I have some SSIS Packages which processes files created or modified
>>> in a perticular folders.
>>>
>>> Now I dont want these Packages to be running continuously n keep
>>> monitoring those folders (each package has its own folder to watch
>>> for) as they will be blocking memory n resources.
>>>
>>> So, I thought of writing seperate program that monitors these
>>> folders and fires appropriate SSIS package.
>>>
>>> Now I am in doubt about what project to go for:
>>>
>>> 1. A SSIS Package that uses WMI Event Watcher.
>>> or
>>> 2. A .Net Service that uses .Net File Watcher and fires SSIS
>>> Packages
>>> Which solution is more applicable n best to go for in terms of
>>> optimised resource utilization.
>>> Thanks,
>>> Sachin.