Your package is using more memory than the server can allocate. When this happens, it creates temporary files on disk to cope with memory situation. By default, this is going to write to the BufferTempStoragePath
value in your Data Flow Task. If you have not provided this value, then those files will be defaulted to the OS's temporary file location. This is typically the C: which when you fill can cause instability. That's bad (tm)
When this occurs, you have 4 options to you.
- Change the Property on each of your Data Flow Tasks to explicitly define a location for BufferTempStoragePath. This is usually the least impactful to your process but does not address the root cause of paging to disk.
- Rework your overall package to have no parallel operations occurring when this Data Flow fires.
- Adjust the BufferRows (approx) to a smaller number to allow fewer rows into pipeline which would result in less paging.
- Rework your data flow to use fewer async transformations. This article is a good starting point to identify the memory intensive transformations
Reference on buffer location What is the actual use of buffer temp and blob temp in ssis