August 2, 2012 at 6:39 am
Hi,
I am trying to move a collection of SSIS packages from one server to another and am running into memory issues.
The development server has got SQL 2008 R2, Analysis Services and Hyper V with 3 active VMS (with a total of 5 GB allocated to them). The Development server has got 64GB of RAM. SQL is allocated 15GB of RAM.
My production server has also got 64GB of RAM, with two Hyper V machines on it (using 8 GB of RAM).
SQL is configured to use a maximum of 8GB).
When I run my SSIS packages I run into buffer issues, despite SSIS stating that the system is under a 37% load:
The system reports 37 percent memory load.
There are 68715253760 bytes of physical memory
with 43281465344 bytes free.
There are 2147352576 bytes of virtual memory
with 32124928 bytes free.
The paging file has 137498677248 bytes
with 110994685952 bytes free.
A buffer failed while allocating
1703856 bytes.
There is plenty of available memory and the buffer sizes between the two machines are the same.
Can anyone suggest an area for me to investigate?
Many thanks,
Graham
August 2, 2012 at 7:19 am
Can you post the full text of the error message?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
August 2, 2012 at 8:07 am
Hi,
I have set SSIS to log the errors to a SQL Server table, and I have just saved them to a text file (attached - but I have commented out the server and account details).
The interesting bits are:
ID Event DataCode Message
61User:OnError -1073450936
(this is repeated until)
656User:OnError -1073450990 A buffer failed while allocating 1703856 bytes.
673673User:OnError -1073450991 The system reports 37 percent memory load. There are 68715253760 bytes of physical memory with 43281465344 bytes free. There are 2147352576 bytes of virtual memory with 32124928 bytes free. The paging file has 137498677248 bytes with 110994685952 bytes free.
I find it odd that there are a number of errors with no message detail.
At present I have configured the logging only to display error information, I can amend this is necessary.
Many thanks,
Graham
August 3, 2012 at 3:47 am
Hi,
I have been able to get the package to run by running it within BIDS on the live server. Not ideal but it does seem to prove that it can work.
When the package is executed via the DTExec utility I seem to encounter the memory issue.
I have checked and it is using the 64bit version of DTExec when the SSIS package is double clicked, which is what I believe BIDS runs under as the Run64BitRuntime option is set to True.
I will test the package running the 32 bit version of the DTExec utility to see if that helps.
Has anyone encountered this kind of issue?
Many thanks,
Graham
August 3, 2012 at 6:35 am
It appears I was wrong!
GRussell31 (8/3/2012)
I have checked and it is using the 64bit version of DTExec when the SSIS package is double clicked, which is what I believe BIDS runs under as the Run64BitRuntime option is set to True.
When double clicking on the SSIS package in Windows Explorer it was actually executing the 32bit version of DTExec. Which is odd as opening a command prompt and typing DTExec displays the 64bit version.
When I ran the 64bit version of DTExec the process (referencing the exe directly via a batch file) seems to be running successfully and running the the 32bit version (again via a batch file) produced errors with memory issues.
I'll now make sure that I am referencing the 64bit exe directly as that seems to work.
Hope that helps,
Graham
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply