January 4, 2010 at 8:54 am
I am getting memory errors when running SSIS pkgs like
There is insufficient memory available in the buffer pool
Currently i have 4GB of Memory, does it mean i have to look for more memory on this machine.
Thanks
January 4, 2010 at 8:58 am
January 4, 2010 at 9:04 am
3277 MB and AWE enabled
January 4, 2010 at 9:07 am
Tara-1044200 (1/4/2010)
3277 MB and AWE enabled
OK, great.
What version of Windows are you using?
What Edition of SQL Server are you using?
Can you also review the Windows Performance Monitor Counters for SQL Server, Total Server Memory and Targe Server Memory.
I suspect that there is not enough memory available for SQL Server but that is what we are looking to validate.
Some Notes on your Specific Error
802 - There is insufficient memory available in the buffer pool.
Causes
This error does not necessarily indicate an out-of-memory condition. It might indicate that the buffer pool memory is used by someone else. In SQL Server 2005, this error should be relatively rare.
Taken from Troubleshooting Performance Problems in SQL Server 2005
Regards,
January 4, 2010 at 9:08 am
Looks like that you are running short of Memory on that machine.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
January 4, 2010 at 9:28 am
unfortunately we have win 2003 standard which will not allow to add more memory.
January 4, 2010 at 9:30 am
What is your SSIS package doing?
Perhaps ther is scope for improvement here?
January 4, 2010 at 5:50 pm
If you do not have over more than 4GB of memory in the machine, then enabling AWE will do nothing for you. It is meant to take advantage of memory above the 4GB limit that the OS is accessing via the PAE boot.ini startup parameter.
If your machine has only 3-4GB of memory and you suspect a memory pressure issue, you could try adding the /3GB switch. This will limit the OS to 1GB of memory, leaving the rest for applications to take advantage of. Also, I would make sure your max memory setting is not too high where SQL is trying to take more memory than the system can handle.
This may take a little bit of trial-and-error to identify and resolve.
Joie Andrew
"Since 1982"
January 4, 2010 at 6:01 pm
Where is the SSIS package being run from; On the SQL Server or a PC?
Only reason I ask, I have gotten this message once when I was testing SSIS package from my machine and noticed that virtual memory on the PC was very low. It had nothing to do with SQL Server.
All other posts have valid suggestions, so please do explore them first.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply