I am currently using a SSIS WMI task to watch a folder, which runs in a for-each loop, until a file is dropped into the folder. Looking at memory usage, it seems like the longer the package runs, the more memory that the package takes, even when the package doesn't look to be doing much, other than checking over and over whether the folder has a new file.
I have created the package so that it will stop running after a file does finally appear, resetting its memory usage, but while it is sitting in memory, I don't want it to keep increasing in size, until a file can arrive, as some of these packages may process files that arrive once every few weeks.
Can anyone suggest any way I can "lighten" the footprint of the package, while it sits in memory for a long time? The memory usage looks to never go down, only up. There are two processes in my task manager, one of which is "SQL Server Integration Services Execute Package Utility" and the other is "SSIS Execution Package". Has anyone else had experience with packages that don't really complete, and will just keep constantly running?
Edit: Oops was meant to put this in the SSIS forum; the server I am deploying to is SQL server 2016 though. Don't see an option to change it now, or delete my post...