June 14, 2005 at 11:02 am
My server runs Windows 2000 Advanced Server sp4 and SQL Server 2000 sp3. The server has 8GB RAM.
Recently, SQL Server Errorlog keeps showing the following errors:
WARNING: Failed to reserve contiguous memory of Size= 35979264.
Query Memory Manager: Grants=2 Waiting=0 Maximum=98092 Available=24371
Global Memory Objects: Resource=2160 Locks=8904
SQLCache=94 Replication=2
LockBytes=2 ServerGlobal=48
Xact=72
Dynamic Memory Manager: Stolen=12857 OS Reserved=10448
OS Committed=10415
OS In Use=10390
Query Plan=972 Optimizer=0
General=3584
Utilities=724 Connection=9213
Procedure Cache: TotalProcs=267 TotalPages=669 InUsePages=272
Buffer Counts: Commited=208672 Target=208672 Hashed=177806
InternalReservation=668 ExternalReservation=56673 Min Free=1024
Buffer Distribution: Stolen=29237 Free=960 Procedures=669
Inram=0 Dirty=1268 Kept=0
I/O=101, Latched=359, Other=176078
Insufficient memory available..
Error: 17803, Severity: 20, State: 12
I have seen KB article 891719 about this error and that SP 4 will fix this problem but I'm not sure if it applies to my error because in the KB it states that "...the most significant information is that Free value is 0 and Commited value is typically more than 10GB". In my case Free=960 and Commited=208672."
I also noticed that this problems arises when user runs a SQLDMO application.
Does anybody have the same issue ? Will SQL Server SP4 really fix this problem ?
Thanks...Jimmy
June 15, 2005 at 5:15 am
I can't help with your exact query - but - there's a posting to say that sql dmo is not thread safe and can cause memory leaks and such. NB sp4 has a bug that means it doesn't work with awe.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
June 20, 2005 at 6:24 am
Do you have AWE enabled?
There is an error in the SP4 regarding the AWE.
Bye
Gabor
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply