Memory pressure issues

  • Thanks for the update - we have load tested the critical update to SP2 in our test cluster and have had no problems. I have scheduled for the Friday's systems time this installation of this SP2 update and have change the startup parms to include -g512.

  • I would be interested in hearing the resolution to your issue, as we just started seeing similar issues last week and are lost on what to do.

  • Hi,

    We still have not applied the SP2 on our production server and have not seen any more memory pressure errors since we put the -g512 switch parameter in our startup. We wanted to run our server for a full month without any reboots to be sure the problem is solved and it looks like it took care of it. I have scheduled to apply the SP2 to our production server next week.

    Isabelle

    Thanks!
    Bea Isabelle

  • Exactly what fixed our problem - the -g512 switch. We had our machines at SP2 level while we were having this problem.

  • What needs to be in the path with the -g512 switch?

    I currently have:

    -dC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\mastlog.ldf

  • -dC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\mastlog.ldf;-g512

  • Thank you Az.

  • (nevermind - forgot to read subsequent pages)

  • You can try to check if this caused by any CLR. Examples of how to find CLR assembly: http://msdn.microsoft.com/en-us/library/foo9fe0d4fd-950a-4274-a493-85e776278045.aspx

    Memory errors on SQL Server 2005 32bit related to CLR objects: http://support.microsoft.com/kb/969962

Viewing 9 posts - 16 through 23 (of 23 total)

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