SQL Server Performance

Memory Leak MS SQL 2005

Discussion in 'SQL Server 2005 General DBA Questions' started by nupe02, Jan 14, 2009.

  1. nupe02 New Member

    I've just notice these error messages has been popping up in the error log several times a day for the last week or two after returning from vacation:

    AppDomain 3 (XXXXX.dbo[runtime].2) is marked for unload due to memory pressure.
    2009-01-05 14:06:06.510 spid1s AppDomain 3 (XXXX.dbo[runtime].2) unloaded.
    2009-01-05 14:14:52.990 spid431 AppDomain 4 (XXXX.dbo[runtime].3) created.
    2009-01-05 15:45:26.780 spid1s AppDomain 4 (XXXX.dbo[runtime].3) is marked for unload due to memory pressure.
    2009-01-05 15:45:26.780 spid1s AppDomain 4 (XXXX.dbo[runtime].3) unloaded.
    2009-01-05 15:54:47.310 spid324 AppDomain 5 (XXXX.dbo[runtime].4) created.
    2009-01-14 11:21:06.710 spid190 AppDomain 25 (APTIFY.dbo[runtime].24) created.
    2009-01-14 11:34:09.970 spid102 AppDomain 25 (APTIFY.dbo[runtime].24) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
    2009-01-14 11:34:10.000 spid102 AppDomain 25 (APTIFY.dbo[runtime].24) unloaded.
    2009-01-14 11:51:20.700 spid135 AppDomain 26 (APTIFY.dbo[runtime].25) created.

    It's a stand alone production box, Windows 2003 (SP2) with 3GB of Ram with MS SQL 2005 SP2 ver.9.00.3042

    No new procedures have been added from my knowledge, and the sp_config settings hasn't been change (says the other DBA).

    Will MS latest Service Pack fix this problem or is there some program not releasing it memory on completion?

    Suggestions Please.
  2. satya Moderator

Share This Page