Post reply

Buffer memory

  • April 10, 2011 at 10:18 pm

    #248691

    We have a ssis package run and failed with some error like below:

    The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. 128 buffers were considered and 125 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.

    Then after about half an hour , we run the Package again, it succeeded.

    What does this message mean, and what can we do so that we can run the package right away instead of waiting for half an hour and run it?

    Thanks

  • April 10, 2011 at 10:36 pm

    #1309647

    How is your server configured?

    32 or 64 bit?

    How much RAM, and what is the MAX Sql Server Memory?

    Is lock pages in memory enabled and have you added the 845 trace flag?

    All these will affect the answer to your question.

    Leo

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • April 10, 2011 at 11:00 pm

    #1309653

    I checked this is a window 2003, 32 bits, 2 gb memory.

    The memory setup uses the default of sql server.

    Thanks

  • April 11, 2011 at 1:36 am

    #1309686

    annasql (4/10/2011)

    I checked this is a window 2003, 32 bits, 2 gb memory.

    The memory setup uses the default of sql server.

    Thanks

    Your box have only 2 GB ram?

    Muthukkumaran Kaliyamoorthy
    https://www.sqlserverblogforum.com/

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply