Showing posts with label monitor. Show all posts
Showing posts with label monitor. Show all posts

Friday, March 23, 2012

Merge Agent

SQL Server Enterprise manager showing Distribution database as SUSPECT and
in result replication monitor do not show any information about replication
agent(Merge agent etc).
I detach database and try to re attach but system showing that database cant
be attached as "log scan" to those file is failed(reflecting files
corrupted).
I attach backup of distribution mdf and ldf file, this time it attached
sucessfully.
BUT the problem remains same, i.e REPLICATION MONITOR IS NOT SHOWING ANY
INFORMATION ABOUT MERGE AGENT.
NOTE. now distribution databse have merge agents record in "msmerge_agents"
table.
Thanks in advance
Best thing to do is restore from back up. Other than that you might try a
sp_attach_single_file_db
Then follow these instructions
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Anjaana Rahi" <anjaanarahi@.gmail.com> wrote in message
news:OgjgwZhBGHA.2704@.TK2MSFTNGP15.phx.gbl...
> SQL Server Enterprise manager showing Distribution database as SUSPECT
> and
> in result replication monitor do not show any information about
> replication
> agent(Merge agent etc).
> I detach database and try to re attach but system showing that database
> cant
> be attached as "log scan" to those file is failed(reflecting files
> corrupted).
> I attach backup of distribution mdf and ldf file, this time it attached
> sucessfully.
> BUT the problem remains same, i.e REPLICATION MONITOR IS NOT SHOWING ANY
> INFORMATION ABOUT MERGE AGENT.
> NOTE. now distribution databse have merge agents record in
> "msmerge_agents"
> table.
> Thanks in advance
>
>
|||Oops, sorry I missed the part about how your backup worked (but the merge
agents are now missing).
Try to script out the publications, then drop them and do a no-sync.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Anjaana Rahi" <anjaanarahi@.gmail.com> wrote in message
news:OgjgwZhBGHA.2704@.TK2MSFTNGP15.phx.gbl...
> SQL Server Enterprise manager showing Distribution database as SUSPECT
> and
> in result replication monitor do not show any information about
> replication
> agent(Merge agent etc).
> I detach database and try to re attach but system showing that database
> cant
> be attached as "log scan" to those file is failed(reflecting files
> corrupted).
> I attach backup of distribution mdf and ldf file, this time it attached
> sucessfully.
> BUT the problem remains same, i.e REPLICATION MONITOR IS NOT SHOWING ANY
> INFORMATION ABOUT MERGE AGENT.
> NOTE. now distribution databse have merge agents record in
> "msmerge_agents"
> table.
> Thanks in advance
>
>

Wednesday, March 21, 2012

MemToLeave area! How to monitor?

Please, take a look at "Inside SQL Server 2000's Memory Management Facilities" by Ken Henderson:
http://msdn.microsoft.com/library/de...v_01262004.asp
"... None of the tools you typically use to inspect application memory use (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by individual processes. There's no indication of the amount of AWE memory used by each process, nor is this
memory included in the working set size reported for a given process ..."
Thanks,
-Ivan
--Original Message--
From: james
Posted At: Tuesday, February 28, 2006 6:52 AM
Posted To: microsoft.public.sqlserver.server
Conversation: MemToLeave area! How to monitor?
Subject: MemToLeave area! How to monitor?
Gurus,
Occasionally I get the error of "WARNING: Failed to reserve contiguous memory of Size= 65536."
What is the unit for this size, is it bytes or KB? Additionally,
I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up maximum for Sql server.
If I look at Perfmon counter of Process->Private bytes for sql server process it gives me 224 MB.
If I look at sqlserver.exe process on task manager it gives me 215MB.
If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
I would like to know, How can I calculate exactly how much memory is being assigned and how much in use from MemToLeave area by looking at above mentioned counters or any other perfmon or dbcc counters?
I really appreciate any input on this matter.
Thanks Ivan. I had already checked that article and also few other google
search but didn't get the answer.
<ivanpe@.online.microsoft.com> wrote in message
news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
> Please, take a look at "Inside SQL Server 2000's Memory Management
> Facilities" by Ken Henderson:
> http://msdn.microsoft.com/library/de...v_01262004.asp
> "... None of the tools you typically use to inspect application memory use
> (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by
> individual processes. There's no indication of the amount of AWE memory
> used by each process, nor is this memory included in the working set size
> reported for a given process ..."
> Thanks,
> -Ivan
> --Original Message--
> From: james
> Posted At: Tuesday, February 28, 2006 6:52 AM
> Posted To: microsoft.public.sqlserver.server
> Conversation: MemToLeave area! How to monitor?
> Subject: MemToLeave area! How to monitor?
>
> Gurus,
> Occasionally I get the error of "WARNING: Failed to reserve contiguous
> memory of Size= 65536."
> What is the unit for this size, is it bytes or KB? Additionally,
> I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on
> AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up
> maximum for Sql server.
> If I look at Perfmon counter of Process->Private bytes for sql server
> process it gives me 224 MB.
> If I look at sqlserver.exe process on task manager it gives me 215MB.
> If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
> I would like to know, How can I calculate exactly how much memory is being
> assigned and how much in use from MemToLeave area by looking at above
> mentioned counters or any other perfmon or dbcc counters?
> I really appreciate any input on this matter.
|||James,
The unit of measure in the message you list is bytes, not KB. Basically,
the memory mgr is failing to reserve 64KB of memory.
The numbers you report from the various monitoring tools don't sound
surprising -- they all measure different things. For example,
Process:Private Bytes is a measure of _committed_ virtual memory, not
reserved. -G controls the region set aside for MTL, not committed or
reserved -- free. That virtual memory is reserved and committed as needed
by the various memory consumers running inside the SQL Server process.
Also, on SS2K, AWE can't be used for anything except caching data and index
pages. Regular MTL allocations never come from AWE.
Keep in mind that the MTL region is really not a region at all but just
refers to the memory left over once the BPool takes what it needs. It's the
unused virtual memory in the process's virtual address space. -G can grow
or shrink this area, but it basically only amounts to unused memory within
the process.
Allocations by external consumers (COM objects, xprocs (usually), OLEDB
providers, etc.) come from MTL. Also, allocations by the server itself that
are >8KB are serviced from MTL rather than the BPool. This just means that,
at some level, they call VirtualAlloc to allocate VM directly from Windows
rather than using pages already allocated to the BPool.
Accompanying the error message you list should be the equivalent of DBCC
MEMORYSTATUS output. This is more relevant than running the command
yourself because it's taken at the exact moment the error occurred. If I
were you, I'd have a look at the various buckets listed in that report to
see if any of them seem high. Keep in mind that many of them are page
counts, not byte counts, so you need to multiply them by 8KB to get the
exact byte count in use.
Also keep in mind that this error can be caused by extreme fragmentation as
well as over-allocation of memory. IOW, you could have well more than 64KB
available within the process, but no single contiguous block of that size or
larger.
If, after you've worked through the above, you still can't figure out why
the reservation is failing, you might want to contact PSS to help you
troubleshoot it further. They deal with these all the time and should be
able to get you fixed up in no time.
HTH,
-kh
"james" <kush@.brandes.com> wrote in message
news:%23hTPNHLPGHA.720@.TK2MSFTNGP14.phx.gbl...
> Thanks Ivan. I had already checked that article and also few other google
> search but didn't get the answer.
> <ivanpe@.online.microsoft.com> wrote in message
> news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
>

MemToLeave area! How to monitor?

Please, take a look at "Inside SQL Server 2000's Memory Management Facilitie
s" by Ken Henderson:
http://msdn.microsoft.com/library/d...ev_01262004.asp
"... None of the tools you typically use to inspect application memory use (
Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by in
dividual processes. There's no indication of the amount of AWE memory used b
y each process, nor is this
memory included in the working set size reported for a given process ..."
Thanks,
-Ivan
--Original Message--
From: james
Posted At: Tuesday, February 28, 2006 6:52 AM
Posted To: microsoft.public.sqlserver.server
Conversation: MemToLeave area! How to monitor?
Subject: MemToLeave area! How to monitor?
Gurus,
Occasionally I get the error of "WARNING: Failed to reserve contiguous memo
ry of Size= 65536."
What is the unit for this size, is it bytes or KB? Additionally,
I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on A
WE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up ma
ximum for Sql server.
If I look at Perfmon counter of Process->Private bytes for sql server proces
s it gives me 224 MB.
If I look at sqlserver.exe process on task manager it gives me 215MB.
If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
I would like to know, How can I calculate exactly how much memory is being a
ssigned and how much in use from MemToLeave area by looking at above mention
ed counters or any other perfmon or dbcc counters?
I really appreciate any input on this matter.Thanks Ivan. I had already checked that article and also few other google
search but didn't get the answer.
<ivanpe@.online.microsoft.com> wrote in message
news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
> Please, take a look at "Inside SQL Server 2000's Memory Management
> Facilities" by Ken Henderson:
> http://msdn.microsoft.com/library/d...ev_01262004.asp
> "... None of the tools you typically use to inspect application memory use
> (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by
> individual processes. There's no indication of the amount of AWE memory
> used by each process, nor is this memory included in the working set size
> reported for a given process ..."
> Thanks,
> -Ivan
> --Original Message--
> From: james
> Posted At: Tuesday, February 28, 2006 6:52 AM
> Posted To: microsoft.public.sqlserver.server
> Conversation: MemToLeave area! How to monitor?
> Subject: MemToLeave area! How to monitor?
>
> Gurus,
> Occasionally I get the error of "WARNING: Failed to reserve contiguous
> memory of Size= 65536."
> What is the unit for this size, is it bytes or KB? Additionally,
> I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on
> AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up
> maximum for Sql server.
> If I look at Perfmon counter of Process->Private bytes for sql server
> process it gives me 224 MB.
> If I look at sqlserver.exe process on task manager it gives me 215MB.
> If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
> I would like to know, How can I calculate exactly how much memory is being
> assigned and how much in use from MemToLeave area by looking at above
> mentioned counters or any other perfmon or dbcc counters?
> I really appreciate any input on this matter.|||James,
The unit of measure in the message you list is bytes, not KB. Basically,
the memory mgr is failing to reserve 64KB of memory.
The numbers you report from the various monitoring tools don't sound
surprising -- they all measure different things. For example,
Process:Private Bytes is a measure of _committed_ virtual memory, not
reserved. -G controls the region set aside for MTL, not committed or
reserved -- free. That virtual memory is reserved and committed as needed
by the various memory consumers running inside the SQL Server process.
Also, on SS2K, AWE can't be used for anything except caching data and index
pages. Regular MTL allocations never come from AWE.
Keep in mind that the MTL region is really not a region at all but just
refers to the memory left over once the BPool takes what it needs. It's the
unused virtual memory in the process's virtual address space. -G can grow
or shrink this area, but it basically only amounts to unused memory within
the process.
Allocations by external consumers (COM objects, xprocs (usually), OLEDB
providers, etc.) come from MTL. Also, allocations by the server itself that
are >8KB are serviced from MTL rather than the BPool. This just means that,
at some level, they call VirtualAlloc to allocate VM directly from Windows
rather than using pages already allocated to the BPool.
Accompanying the error message you list should be the equivalent of DBCC
MEMORYSTATUS output. This is more relevant than running the command
yourself because it's taken at the exact moment the error occurred. If I
were you, I'd have a look at the various buckets listed in that report to
see if any of them seem high. Keep in mind that many of them are page
counts, not byte counts, so you need to multiply them by 8KB to get the
exact byte count in use.
Also keep in mind that this error can be caused by extreme fragmentation as
well as over-allocation of memory. IOW, you could have well more than 64KB
available within the process, but no single contiguous block of that size or
larger.
If, after you've worked through the above, you still can't figure out why
the reservation is failing, you might want to contact PSS to help you
troubleshoot it further. They deal with these all the time and should be
able to get you fixed up in no time.
HTH,
-kh
"james" <kush@.brandes.com> wrote in message
news:%23hTPNHLPGHA.720@.TK2MSFTNGP14.phx.gbl...
> Thanks Ivan. I had already checked that article and also few other google
> search but didn't get the answer.
> <ivanpe@.online.microsoft.com> wrote in message
> news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
>

MemToLeave area! How to monitor?

Gurus,
Occasionally I get the error of "WARNING: Failed to reserve contiguous
memory of Size= 65536."
What is the unit for this size, is it bytes or KB? Additionally,
I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on
AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up
maximum for Sql server.
If I look at Perfmon counter of Process->Private bytes for sql server
process it gives me 224 MB.
If I look at sqlserver.exe process on task manager it gives me 215MB.
If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
I would like to know, How can I calculate exactly how much memory is being
assigned and how much in use from MemToLeave area by looking at above
mentioned counters or any other perfmon or dbcc counters?
I really appreciate any input on this matter.Please, take a look at "Inside SQL Server 2000's Memory Management Facilities" by Ken Henderson:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqldev/html/sqldev_01262004.asp
"... None of the tools you typically use to inspect application memory use (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by individual processes. There's no indication of the amount of AWE memory used by each process, nor is this memory included in the working set size reported for a given process ..."
Thanks,
-Ivan
--Original Message--
From: james
Posted At: Tuesday, February 28, 2006 6:52 AM
Posted To: microsoft.public.sqlserver.server
Conversation: MemToLeave area! How to monitor?
Subject: MemToLeave area! How to monitor?
Gurus,
Occasionally I get the error of "WARNING: Failed to reserve contiguous memory of Size= 65536."
What is the unit for this size, is it bytes or KB? Additionally,
I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up maximum for Sql server.
If I look at Perfmon counter of Process->Private bytes for sql server process it gives me 224 MB.
If I look at sqlserver.exe process on task manager it gives me 215MB.
If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
I would like to know, How can I calculate exactly how much memory is being assigned and how much in use from MemToLeave area by looking at above mentioned counters or any other perfmon or dbcc counters?
I really appreciate any input on this matter.|||Thanks Ivan. I had already checked that article and also few other google
search but didn't get the answer.
<ivanpe@.online.microsoft.com> wrote in message
news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
> Please, take a look at "Inside SQL Server 2000's Memory Management
> Facilities" by Ken Henderson:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqldev/html/sqldev_01262004.asp
> "... None of the tools you typically use to inspect application memory use
> (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory used by
> individual processes. There's no indication of the amount of AWE memory
> used by each process, nor is this memory included in the working set size
> reported for a given process ..."
> Thanks,
> -Ivan
> --Original Message--
> From: james
> Posted At: Tuesday, February 28, 2006 6:52 AM
> Posted To: microsoft.public.sqlserver.server
> Conversation: MemToLeave area! How to monitor?
> Subject: MemToLeave area! How to monitor?
>
> Gurus,
> Occasionally I get the error of "WARNING: Failed to reserve contiguous
> memory of Size= 65536."
> What is the unit for this size, is it bytes or KB? Additionally,
> I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a on
> AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is set up
> maximum for Sql server.
> If I look at Perfmon counter of Process->Private bytes for sql server
> process it gives me 224 MB.
> If I look at sqlserver.exe process on task manager it gives me 215MB.
> If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
> I would like to know, How can I calculate exactly how much memory is being
> assigned and how much in use from MemToLeave area by looking at above
> mentioned counters or any other perfmon or dbcc counters?
> I really appreciate any input on this matter.|||James,
The unit of measure in the message you list is bytes, not KB. Basically,
the memory mgr is failing to reserve 64KB of memory.
The numbers you report from the various monitoring tools don't sound
surprising -- they all measure different things. For example,
Process:Private Bytes is a measure of _committed_ virtual memory, not
reserved. -G controls the region set aside for MTL, not committed or
reserved -- free. That virtual memory is reserved and committed as needed
by the various memory consumers running inside the SQL Server process.
Also, on SS2K, AWE can't be used for anything except caching data and index
pages. Regular MTL allocations never come from AWE.
Keep in mind that the MTL region is really not a region at all but just
refers to the memory left over once the BPool takes what it needs. It's the
unused virtual memory in the process's virtual address space. -G can grow
or shrink this area, but it basically only amounts to unused memory within
the process.
Allocations by external consumers (COM objects, xprocs (usually), OLEDB
providers, etc.) come from MTL. Also, allocations by the server itself that
are >8KB are serviced from MTL rather than the BPool. This just means that,
at some level, they call VirtualAlloc to allocate VM directly from Windows
rather than using pages already allocated to the BPool.
Accompanying the error message you list should be the equivalent of DBCC
MEMORYSTATUS output. This is more relevant than running the command
yourself because it's taken at the exact moment the error occurred. If I
were you, I'd have a look at the various buckets listed in that report to
see if any of them seem high. Keep in mind that many of them are page
counts, not byte counts, so you need to multiply them by 8KB to get the
exact byte count in use.
Also keep in mind that this error can be caused by extreme fragmentation as
well as over-allocation of memory. IOW, you could have well more than 64KB
available within the process, but no single contiguous block of that size or
larger.
If, after you've worked through the above, you still can't figure out why
the reservation is failing, you might want to contact PSS to help you
troubleshoot it further. They deal with these all the time and should be
able to get you fixed up in no time.
HTH,
-kh
"james" <kush@.brandes.com> wrote in message
news:%23hTPNHLPGHA.720@.TK2MSFTNGP14.phx.gbl...
> Thanks Ivan. I had already checked that article and also few other google
> search but didn't get the answer.
> <ivanpe@.online.microsoft.com> wrote in message
> news:OenNh9IPGHA.3840@.TK2MSFTNGP14.phx.gbl...
>> Please, take a look at "Inside SQL Server 2000's Memory Management
>> Facilities" by Ken Henderson:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqldev/html/sqldev_01262004.asp
>> "... None of the tools you typically use to inspect application memory
>> use (Task Manager, Perfmon/Sysmon, etc.) show the amount of AWE memory
>> used by individual processes. There's no indication of the amount of AWE
>> memory used by each process, nor is this memory included in the working
>> set size reported for a given process ..."
>> Thanks,
>> -Ivan
>> --Original Message--
>> From: james
>> Posted At: Tuesday, February 28, 2006 6:52 AM
>> Posted To: microsoft.public.sqlserver.server
>> Conversation: MemToLeave area! How to monitor?
>> Subject: MemToLeave area! How to monitor?
>>
>> Gurus,
>> Occasionally I get the error of "WARNING: Failed to reserve contiguous
>> memory of Size= 65536."
>> What is the unit for this size, is it bytes or KB? Additionally,
>> I have set up 511 MB for MemToLeave area by adding -g384 for Sql2k SP3a
>> on AWE enabled system. I have total of 16 GB of RAM, of which 14 GB is
>> set up maximum for Sql server.
>> If I look at Perfmon counter of Process->Private bytes for sql server
>> process it gives me 224 MB.
>> If I look at sqlserver.exe process on task manager it gives me 215MB.
>> If I look at DBCC memorystatus, OS in use, it gives me 12 MB.
>> I would like to know, How can I calculate exactly how much memory is
>> being assigned and how much in use from MemToLeave area by looking at
>> above mentioned counters or any other perfmon or dbcc counters?
>> I really appreciate any input on this matter.
>

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:

> I'm using a performance console system monitor to observe memory performan
ce
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physica
l
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.
Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:

> I'm using a performance console system monitor to observe memory performance
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physical
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.

Memory, Available Bytes

I'm using a performance console system monitor to observe memory performance
of a Win 2K server, running 2K SQL server.
The available bytes indicates less than half of the system's total physical
memory of
4 gig. Could this be a possible indication of a memory leak. What, if any
possible
solutions are available. Thanks to everyone for being there to help.Hi
If the Server has 4GB RAM, and is Enterprise Edition of Windows 2000, is the
/3GB flag set in boot.ini ?
If not, only 2GB of the possible 3GB is presented to applications. The other
1GB is always reserved for the OS.
If it is Standard Edition of Windows 2000, supported is only 2GB of the 4GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"coenzyme" wrote:
> I'm using a performance console system monitor to observe memory performance
> of a Win 2K server, running 2K SQL server.
> The available bytes indicates less than half of the system's total physical
> memory of
> 4 gig. Could this be a possible indication of a memory leak. What, if any
> possible
> solutions are available. Thanks to everyone for being there to help.sql

Monday, March 12, 2012

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way.
Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way.
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.
|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> OS
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>
|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way. Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way.
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> OS
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Memory usage 98% is it a bad thing?

I am using Spotlight to monitor my servers.
I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way. :)Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way. :)
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
--
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
>> If you are using the AWE ENabled option with SQL Server, you need to
>> specify the "Max Server Memory" for SQL Server to prevent it from using
>> all available RAM on the server. Make sure you leave enough RAM for the
> OS
>> and any other services running on the server.
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.

Monday, February 20, 2012

Memory management

I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
of the 4 gb installed in the server. How do I reduce the amount of memory
SQL is using?
MBS
Set the MAx Memory setting to the amount you want minus about 300MB and you
should be all set. You can do this via sp_configure or ssms.
Andrew J. Kelly SQL MVP
"MBS" <who@.nowhere.com> wrote in message
news:H8CdnbIX_t1gHsvYnZ2dnUVZ_uednZ2d@.suscom.com.. .
>I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
>databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
>of the 4 gb installed in the server. How do I reduce the amount of memory
>SQL is using?
> MBS
>

Memory management

I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
of the 4 gb installed in the server. How do I reduce the amount of memory
SQL is using?
MBSSet the MAx Memory setting to the amount you want minus about 300MB and you
should be all set. You can do this via sp_configure or ssms.
Andrew J. Kelly SQL MVP
"MBS" <who@.nowhere.com> wrote in message
news:H8CdnbIX_t1gHsvYnZ2dnUVZ_uednZ2d@.su
scom.com...
>I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
>databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
>of the 4 gb installed in the server. How do I reduce the amount of memory
>SQL is using?
> MBS
>

Memory management

I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
of the 4 gb installed in the server. How do I reduce the amount of memory
SQL is using?
MBSSet the MAx Memory setting to the amount you want minus about 300MB and you
should be all set. You can do this via sp_configure or ssms.
--
Andrew J. Kelly SQL MVP
"MBS" <who@.nowhere.com> wrote in message
news:H8CdnbIX_t1gHsvYnZ2dnUVZ_uednZ2d@.suscom.com...
>I am running MS sql 2005 workgroup on a SBS 2003 - R2 server. The only
>databases are Sharepoint and Small Business Monitor. SQL is using over 3 gb
>of the 4 gb installed in the server. How do I reduce the amount of memory
>SQL is using?
> MBS
>