Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Out of Memory Problem

Status
Not open for further replies.

MSSQLServer2005

Programmer
Nov 16, 2006
2
IN
Hi,
Me and my team is using SSIS installed in one machine, using different login ids. We are trying to create/modify/execute the packages, but everytime we are facing out of memory issue. We encounter this problem while saving, executing and closing the window. We are not working on the same package or anything. We are all working on different packages. Both the drives in the machine has more than 20 GB of free space (each). Moreover, the machine has 3GB of ram.
If anytone has faced this problem before, then please suggest the solution.
 
SSIS is a HUGE memory hog. If you're all working on the same server, it's no wonder you're getting the error.

Try installing the SQL Server 2k5 development tools on your desktops and work on the packages from there. Then you can upload the packages to the server when you're done. Recommended minimum RAM for a desktop with a single person using SSIS is 2 GB (that's what I have).



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
The following is the exact error that we are facing.


1) [DTS.Pipeline] Information: The buffer manager failed a memory allocation call for 4849256 bytes,
but was unable to swap out any buffers to relieve memory pressure. 7 buffers were considered and 7
were locked. Either not enough memory is available to the pipeline because not enough are installed,
other processes were using it, or too many buffers are locked.
2) [DTS.Pipeline] Error: A buffer failed while allocating 4849256 bytes.
3) [DTS.Pipeline] Error: The system reports 94 percent memory load. There are 3757539328 bytes of
physical memory with 217817088 bytes free. There are 2147352576 bytes of virtual memory with 1226752000
bytes free. The paging file has 7886893056 bytes with 7634944 bytes free.
4) [DTS.Pipeline] Error: The Data Flow task failed to create a buffer to call PrimeOutput for output
"ALL_FINAL" (1605) on component "Union All Output 1" (1607). This error usually occurs due to an
out-of-memory condition.
5) [DTS.Pipeline] Error: Thread "WorkThread1" has exited with error code 0x8007000E.
6) [DTS.Pipeline] Error: Thread "WorkThread2" received a shutdown signal and is terminating. The
user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.
7) [DTS.Pipeline] Error: Thread "WorkThread2" has exited with error code 0xC0047039.
8) [DTS.Pipeline] Error: The ProcessInput method on component "ALL_ERROR" (160) failed with error
code 0xC0047020. The identified component returned an error from the ProcessInput method. The error
is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
9) [DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0xC0047020.


Regards

 
My workstation has 1.5 Gigs of RAM in it, and I often get funky memory errors when running packages which move large amounts of data.

An excellent first step would be do install the client tools on your workstation and test the packages there.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top