I have an 2005 SSIS package that runs on a Windows 2003 Server hitting a SQL Server 2005 database on the same server. I have a package that SQL Server Job Scheduler reports executing successfully, yet on certain days the functionality in side the package does not run. Desperate for answers, I have been searching the application’s audit logs and Windows Event Viewer. I noticed that days this package does not execute coincide s with days that another package stops (does not fail how you would typically expect a package to fail) due to high memory usage. The other thing I noticed by searching through the Windows Event Viewer is that even though SQL Server Job Scheduler claims to of executed the package successfully, there is no record of the event in the Event Viewer.
After all of that, my question is: are there any reports of bugs with the SQL Server / Windows Server combination regarding executing packages after high server memory usage in the same day? Regardless of the first, any suggestions on a work around?
Other related facts: due to other projects in the works, I am not authorized to modify the packages that fails when the memory usage is high.. I’m only allowed to restart the package.
Please let me know if I need to provide additional details.
Additional Details 2012.01.30
Recently an 8 GB stick of memory was removed from the server. SQL Server’s max allocation was set to 30 GB. Once the stick was removed, only 24 GB remained.
2012.02.10: I was given the approval to rewrite the memory leaking package.
I determined that the execution of the previously mention rules in a foreach loop caused the memory leak on the server. I removed this looping package and replaced it with a stored procedure.
Since this change went into effect, no out of memory exceptions have occurred in the problem package and my package is running successfully.