Post reply

AppDomain 12 (mssqlsystemresource.dbo[runtime].11) is marked for unload due to memory pressure.

  • August 10, 2012 at 3:44 am

    #262550

    Hi All,

    I am getting these errors in sql log and windows event log as,

    1)AppDomain 12 (mssqlsystemresource.dbo[runtime].11) is marked for unload due to memory pressure.

    2)AppDomain 12 (mssqlsystemresource.dbo[runtime].11) unloaded.

    The SQL Standard Edition version 2008R2 having build 10.50.1600.1 (RTM).

    Unable to identify what is triggering these error's or what is cause behind that.

    I have checked the CLR it is disabled on the server.

    Please help to understand these errors or any solution if possible

    Thanks in advance

    Vinod

  • August 10, 2012 at 7:55 am

    #1524439

    how much memory on the server and what is the sql max memory configured as?

    sql's max memory setting controls the buffer pool, not the memory used for the app domains for sql clr. If max memory is set is too high, then some external process to sql on the box could be consuming excess memory, and sql is unloading the app domains reduce external memory pressure.

  • August 10, 2012 at 8:08 am

    #1524450

    32 bit or 64 bit SQL?

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 16, 2012 at 3:34 am

    #1526423

    Hi All,

    Thanks for all your responses. I was out of office for couple of days.

    @springtowndba : These are the details for your reference the total RAM on server is 48GB. SQL is Std Edition 64 bit. The max server memory setting for SQL Server is default one.

    @Gail : The SQL is 64 bit Standard Edition.

    What need to done from SQL front. Do I need to add additional RAM. We have already planned for Service pack update on the server as its build is RTM.

    Looking for the solution.......

    Thanks

  • August 16, 2012 at 3:41 am

    #1526430

    Start by setting max server memory to a sensible value.

    Chapter 4: http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 16, 2012 at 4:58 am

    #1526465

    Hi,

    @Gail: One question on this as suggested by you. Does it make sense to set max sever memory for this particular issue?

    However I going through link and the pdf doc as provided by you.

    Thanks again

  • August 16, 2012 at 5:13 am

    #1526484

    Yes.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 7 posts - 1 through 6 (of 6 total)

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