Unknown,AppDomain 6 (database_name.dbo[runtime].5) is marked for unload due to memory pressure.

Discussion:

(too old to reply)

siddu

2009-09-10 07:41:17 UTC

Hi All,

Can anyone throw light on this error which I am getting in the sql server
erorr log.

09/09/2009 18:01:38,spid1s,Unknown,AppDomain 6
(database_name.dbo[runtime].5) unloaded.
09/09/2009 18:01:38,spid1s,Unknown,AppDomain 6
(database_name.dbo[runtime].5) is marked for unload due to memory pressure

I am unable to figure out why this occurs and what is causing this.
I am using sql server2005 version 9.0.4035 (X64) standard edition.

Thanks in advance,
Siddu

Alberto Silva, MVP

2009-09-10 11:01:20 UTC

Permalink

Hi,
This newsgroup is dedicated to SQL Compact, not the 'real' Server editions,
so you'll be luckier in a more appropriate newsgroup.
--
Alberto Silva
http://www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development

Post by siddu
Hi All,
Can anyone throw light on this error which I am getting in the sql server
erorr log.
09/09/2009 18:01:38,spid1s,Unknown,AppDomain 6
(database_name.dbo[runtime].5) unloaded.
09/09/2009 18:01:38,spid1s,Unknown,AppDomain 6
(database_name.dbo[runtime].5) is marked for unload due to memory pressure
I am unable to figure out why this occurs and what is causing this.
I am using sql server2005 version 9.0.4035 (X64) standard edition.
Thanks in advance,
Siddu
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4413 (20090910) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4413 (20090910) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Russell Fields

2009-09-11 13:15:10 UTC

Permalink

Siddu,

I don't see that you have yet asked in another group, but here are a couple
of reasons from the past.
http://support.microsoft.com/kb/917271
http://support.microsoft.com/kb/928083

However, your build level (SP3) should certainly already contain these
fixes. The people that I could find that still had the problem post-hotfix
were using CLR routines. Does you problem center on CLR use?

If so, you might change (or start using) the -g startup option. It defaults
to 256 MB, but I had problems and (for my instance) upping it to 384 MB
resolved the problems.

Likewise, if the CLR seems to be the root of the problem, you should also
read this to see if there are any CLR coding practices that might need to be
adjusted.
http://www.sqlskills.com/resources/Whitepapers/SQL%20Server%20DBA%20Guide%20to%20SQLCLR.htm#_Toc110615520

FWIW,
RLF