February 15, 2007 at 7:56 am
Hi all, can someone please tell me what are these messages from my sqlserver log? Thanks!
--WARNING: Failed to reserve contiguous memory of Size= 65536.
--Buffer Distribution: Stolen=35970 Free=2149 Procedures=40220
Inram=0 Dirty=6919 Kept=0
I/O=0, Latched=241, Other=954399
--Buffer Counts: Commited=1039898 Target=1039898 Hashed=961431
InternalReservation=416 ExternalReservation=0 Min Free=1872 Visible= 191328
--Procedure Cache: TotalProcs=911 TotalPages=40220 InUsePages=20300
--Dynamic Memory Manager: Stolen=41170 OS Reserved=3872
OS Committed=3850
OS In Use=3789
Query Plan=40209 Optimizer=0
General=3553
Utilities=6 Connection=292
--Global Memory Objects: Resource=1490 Locks=913
SQLCache=1690 Replication=2
LockBytes=2 ServerGlobal=21
Xact=49
--Query Memory Manager: Grants=1 Waiting=0 Maximum=127764 Available=92617
February 15, 2007 at 9:23 am
Hello,
Please refere these links and you might get some clue:
http://support.microsoft.com/kb/903002
http://www.examnotes.net/archive79-2002-10-69316.html
Hope this helps. Please post back any details which might be useful for others.
Thanks
Lucky
February 16, 2007 at 5:51 am
this is generally to do with the memtoleave area and indicates fragmentation of memory. Ken Henderson's book Guru's guide to sql server internals has the only real description of what this is about. I have a server which suffers from this quite badly, there is a fix, look under startup options -g , you can run this in through EM, don't have to use command line.
I looked for packets and couldn't find such a link on my server. It's to do with all sorts of things, xp calls, oledb, out of process calls, large query plans ... You need the book as there's nothing really definitive on the web .. you'll find some stuff at microsoft on the error too.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 16, 2007 at 8:14 am
THank you all. I'll check on it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply