CozyRoc (12/19/2008)
There is no place where you specify global limit for SSIS processes. You control memory consumption granulary, by controlling specific SSIS tasks memory constraints. A good example is the Lookup transformation where you can limit the amount of memory in use for caching. The SSIS data flow task processes data in chunks, so if you don't use large buffers you will not have problems. I think you have to be more concerned about CPU contention. SSIS can be quite CPU intensive.p.s.
I'm wondering why you are not using 64bit OS if you have 8GB of memory?
We are thinking of moving to 64-bit, and it can't be soon enough. 🙂
I guess then SSIS is limited by the default 2 GB of virtual memory available to processes in 32-bit OS?
I wonder why MS did not think of providing an API for configuring memory at the global level, just as can be done in the db-engine and SSAS instances... It seems like a serious omission to me.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]