March 29, 2012 at 4:09 pm
We have a sql server 32 bits server for sql server 2005 database and integration service.
Recently our ssis package failed with some information like below:
"The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. 98 buffers were considered and 94 were locked. Either not enough memory is available to the pipeline because not enough is installed, other processes are using it, or too many buffers are locked."
We add memory to 4 GB, (it still shows 3.5 GB in computer property screen)
Now I would like to configure the max server memory for SQL server, what value should I set it to?
What else should I do?
Thanks
March 29, 2012 at 4:17 pm
how much memory did you have before?
As its 32bit SQL engine wont be able to take more than 2GB and will probably top out around the 1.7GB mark, so no need to set max memory.
SSIS will use memory separate from that.
---------------------------------------------------------------------
March 29, 2012 at 4:48 pm
We only had 2 GB memory.
So after we extended 4 gb, will that help with SSIS?
How about the quoted error message in my original post? How to fix that?
March 30, 2012 at 4:17 am
the extra memory will help with SSIS and should alleviate the error if its enough extra memory
---------------------------------------------------------------------
March 30, 2012 at 4:57 am
Please don't post multiple threads for the same problem. http://www.sqlservercentral.com/Forums/Topic1272448-391-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 30, 2012 at 9:55 am
Sorry, I see that one didn't get answered for a while, so start a new one described more clearly
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply