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...
>
Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts
Wednesday, March 21, 2012
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...
>
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.
>
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.
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.
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
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
Memory Warning
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size= 65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
HillaireThere are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
--
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;818095
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
WARNING: Failed to reserve contiguous memory of Size= 65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
HillaireThere are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
--
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/default.aspx?scid=kb;en-us;818095
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
Memory Warning
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
There are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=
> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire
|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/default...b;en-us;818095
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
There are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=
> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire
|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/default...b;en-us;818095
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
Memory Warning
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
HillaireThere are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=
> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/defaul...kb;en-us;818095
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
HillaireThere are certain operations that can only happen in a contiguous block of
memory and this is done in what is called the MemToLeave area. By default
you only have about 256MB allocated for this area and you must have run low.
If this repeats you might considering adding the -g parameter to SQL Server
upon startup and reserve more than 256MB. Have a look at "startup options"
in BooksOnLine for more details.
Andrew J. Kelly SQL MVP
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
> I have the following entries in my sql error log:
> WARNING: Failed to reserve contiguous memory of Size=
> 65536.
> Buffer Distribution: Stolen=4294940950 Free=112
> Procedures=109559
> Inram=0 Dirty=1167 Kept=0
> I/O=0, Latched=206, Other=123974
> Buffer Counts: Commited=208672 Target=208672
> Hashed=125347
> InternalReservation=346 ExternalReservation=58 Min
> Free=128
> Procedure Cache: TotalProcs=10484 TotalPages=109559
> InUsePages=14527
> Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
> OS Committed=36671
> OS In Use=29121
> Query Plan=108697 Optimizer=0
> General=3420
> Utilities=6 Connection=68
> Global Memory Objects: Resource=1808 Locks=77
> SQLCache=653 Replication=2
> LockBytes=2 ServerGlobal=46
> Xact=18
> Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
> Available=165320
> Can anyone help diagnose the problem?
> Thanks,
> Hillaire|||What service pack are on for SQL Server? See if this applies to you:
http://support.microsoft.com/defaul...kb;en-us;818095
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"kelly" <anonymous@.discussions.microsoft.com> wrote in message
news:08d501c46e65$82f1e660$a601280a@.phx.gbl...
I have the following entries in my sql error log:
WARNING: Failed to reserve contiguous memory of Size=
65536.
Buffer Distribution: Stolen=4294940950 Free=112
Procedures=109559
Inram=0 Dirty=1167 Kept=0
I/O=0, Latched=206, Other=123974
Buffer Counts: Commited=208672 Target=208672
Hashed=125347
InternalReservation=346 ExternalReservation=58 Min
Free=128
Procedure Cache: TotalProcs=10484 TotalPages=109559
InUsePages=14527
Dynamic Memory Manager: Stolen=83213 OS Reserved=40456
OS Committed=36671
OS In Use=29121
Query Plan=108697 Optimizer=0
General=3420
Utilities=6 Connection=68
Global Memory Objects: Resource=1808 Locks=77
SQLCache=653 Replication=2
LockBytes=2 ServerGlobal=46
Xact=18
Query Memory Manager: Grants=1 Waiting=0 Maximum=165378
Available=165320
Can anyone help diagnose the problem?
Thanks,
Hillaire
Memory Utilization
Dear all,
One of the server is having 2 GB of RAM and task manager is showing 1.87 GB memory in use.
I have to migrate few databases on the same server.
With high IO Operations.
I know server require more RAM, but how can i prove that server needs more RAM ?
Regards
Mohd Sufian
To 'Prove' it, you need data. These articles will point you in the right direction to get some data.
Performance Audit
http://www.sql-server-performance.com/articles_audit.asp
http://www.sql-server-performance.com/sql_server_performance_audit10.asp
Performance Monitoring
http://www.microsoft.com/technet/prodtechnol/sql/2005/library/operations.mspx Performance WP's
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx Troubleshooting Performance 2005
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.com/sql_server_performance_audit.asp Hardware Performance CheckList
http://www.sql-server-performance.com/ss_performance_monitoring.asp Practical Solution for Monitoring
http://www.sql-server-performance.com/best_sql_server_performance_tips.asp SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=224587 Troubleshooting App Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp Disk Monitoring
http://sqldev.net/misc/WaitTypes.htm Wait Types
http://support.microsoft.com/?id=271509 Script to Monitor Blocking
Performance Tuning -Articles
http://www.sql-server-performance.com/articles_performance.asp
Performance Tuning –Hardware
http://www.sql-server-performance.com/sg_sql_server_performance_article.asp
You can look at some easy PerfMon counters, such as Buffer Cache Hit Ratio, Page Life Expectancy, and Memory Grants Pending to get a better idea about whether you are seeing memory pressure. Memory pressure will also cause increased IO pressure.
Generally speaking, you can hardly go wrong by adding more RAM to SQL Server, especially if you only have`2GB of RAM installed.
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
Rafa
Hi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Take a look at the following URL
http://support.microsoft.com/default...b;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default...b;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>
|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
Rafa
Hi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL% 20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Take a look at the following URL
http://support.microsoft.com/default...b;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default...b;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>
|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa
|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
memory utilization
What do people think is normal for memory utilization? I know that's too
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
Tom
Are there other applications (IIS) competing for memory on this server?
|||SQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>
|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From[vbcol=seagreen]
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
too[vbcol=seagreen]
> slowed.
empty."
> seen
> SQL
> muted
>
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
Tom
Are there other applications (IIS) competing for memory on this server?
|||SQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>
|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From[vbcol=seagreen]
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
too[vbcol=seagreen]
> slowed.
empty."
> seen
> SQL
> muted
>
memory utilization
What do people think is normal for memory utilization? I know that's too
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
TomAre there other applications (IIS) competing for memory on this server?|||SQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
too[vbcol=seagreen]
> slowed.
empty."[vbcol=seagreen]
> seen
> SQL
> muted
>sql
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
TomAre there other applications (IIS) competing for memory on this server?|||SQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
too[vbcol=seagreen]
> slowed.
empty."[vbcol=seagreen]
> seen
> SQL
> muted
>sql
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper tha
n
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Micros
oft%20SQL%20Server\80\Tools\Books\ar
chitec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/defaul...kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeo
n
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with hu
ge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory
?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper t
han
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/defaul...kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\arc
hitec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\adm
insql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and
or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
rchitec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
dminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper tha
n
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Micros
oft%20SQL%20Server\80\Tools\Books\ar
chitec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/defaul...kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa?" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeo
n
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with hu
ge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory
?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper t
han
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/defaul...kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Dual-Xeon
> huge
> memory?
> than
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\arc
hitec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\adm
insql.chm::/ad_1_server_1fnd.htm
Keith
"Rafa" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and
or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
rchitec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microso
ft%20SQL%20Server\80\Tools\Books\a
dminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa?" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
>
>
Memory Utilization
Dear all,
One of the server is having 2 GB of RAM and task manager is showing 1.87 GB memory in use.
I have to migrate few databases on the same server.
With high IO Operations.
I know server require more RAM, but how can i prove that server needs more RAM ?
Regards
Mohd Sufian
To 'Prove' it, you need data. These articles will point you in the right direction to get some data.
Performance Audit
http://www.sql-server-performance.com/articles_audit.asp
http://www.sql-server-performance.com/sql_server_performance_audit10.asp
Performance Monitoring
http://www.microsoft.com/technet/prodtechnol/sql/2005/library/operations.mspx Performance WP's
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx Troubleshooting Performance 2005
http://www.swynk.com/friends/vandenberg/perfmonitor.asp Perfmon counters
http://www.sql-server-performance.com/sql_server_performance_audit.asp Hardware Performance CheckList
http://www.sql-server-performance.com/ss_performance_monitoring.asp Practical Solution for Monitoring
http://www.sql-server-performance.com/best_sql_server_performance_tips.asp SQL 2000 Performance tuning tips
http://www.support.microsoft.com/?id=224587 Troubleshooting App Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_24u1.asp Disk Monitoring
http://sqldev.net/misc/WaitTypes.htm Wait Types
http://support.microsoft.com/?id=271509 Script to Monitor Blocking
Performance Tuning -Articles
http://www.sql-server-performance.com/articles_performance.asp
Performance Tuning –Hardware
http://www.sql-server-performance.com/sg_sql_server_performance_article.asp
You can look at some easy PerfMon counters, such as Buffer Cache Hit Ratio, Page Life Expectancy, and Memory Grants Pending to get a better idea about whether you are seeing memory pressure. Memory pressure will also cause increased IO pressure.
Generally speaking, you can hardly go wrong by adding more RAM to SQL Server, especially if you only have`2GB of RAM installed.
memory utilization
What do people think is normal for memory utilization? I know that's too
broad, so here are some basics.
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
TomSQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
--
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> > What do people think is normal for memory utilization? I know that's
too
> > broad, so here are some basics.
> > MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> > Db 1, size = 2.0 GB
> > Db 2, size = 300MB
> > Db 3, size = 50MB
> > Db 4, size = 30MB
> > Db 5, size = 30MB
> > Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
> slowed.
> > Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> > Sun 61MB
> > Mon 200MB
> > Tues 800MB
> > Wed 1,124MB
> > Thu 1,424MB
> > Fri 1,303MB
> > I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> > unable to allocate from the system paged pool because the pool was
empty."
> > Then I did several updates to address this and got more RAM. I haven't
> seen
> > the errors since, but I haven't waited for them to happen: I'm rebooting
> > every week now. The memory numbers make me suspect SQL Server.
> > Scratching my head. Not sure if my problem is gone, and this is normal
> SQL
> > Server 2000 behavior, or if my problem is still lurking and I've only
> muted
> > it a bit.
> > Any thoughts greatly appreciated.
> > Tom|||Dear reader,
I have the same problem!! My sqlservr.exe in the taskmanager is growing everyday.
The SQL is clustered.
Some times the user is loosing connection and I have a eventID 2020 in my eventviewer.
Microsoft writes to do some registry adjustments in the
hkey_local_machines\system\Currentcontrolset\contr ol\session\mamager\Memory Managent
Create PoolUsagemaximum
and
PagedPoolSize
see http://support.microsoft.com/defaul...kb;en-us;312362
Is there anyone who has another suggestion for this problem??
Or is the Microsoftsolution the only one.
Memory Utilization
Guys,
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa®" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> > Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> > huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> > memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> > than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>
I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
can use the whole memory for the SQL Server service...
Just as a 2GB server that I had before, monitoring with Task Manager I see
that the memory utilization don't grow up more than 1,84gb... Even with huge
processing and disk reading... So my question is, is there any kind of
special configuration that you must set to let server use the whole memory?
I know about AWE, but I thought AWE is just for servers who break the 4GB
boundary... Would like to know why the memory utilization don't go upper than
1,84gb, even setting this as a fixed value in Server configuration...
Thx,
RafaHi,
What edition of SQL Server you are using? Only Enterprise or Developer
editions of SQL server supports more than 2 GB memory.
Sheck the version of SQL Server using
Select @.@.version
Thanks
Hari
SQL Server MVP
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Take a look at the following URL
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
There is a \3GB switch
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||According to Books Online
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn.htm)
the Standard Edition of SQL Server will not use more than 2GB of RAM.
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Hi,
Try /3gb switch in boot.ini
"Rafa®" wrote:
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Well, it's the Enterprise Edition...
What does /3gb in boot.ini?
"Wayne Snyder" wrote:
> Take a look at the following URL
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
> There is a \3GB switch
>
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>|||Since you are running on Enterprise Edition you could try using /3GB and or
/PAE within boot.ini.
You will then probably want to specify the memory usage within SQL Server
Using AWE Memory on Windows 2000
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
Managing AWE Memory
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
--
Keith
"Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> Guys,
> I have a server running MS-SQL SP3. The server configuration is a
> Dual-Xeon
> 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> can use the whole memory for the SQL Server service...
> Just as a 2GB server that I had before, monitoring with Task Manager I see
> that the memory utilization don't grow up more than 1,84gb... Even with
> huge
> processing and disk reading... So my question is, is there any kind of
> special configuration that you must set to let server use the whole
> memory?
> I know about AWE, but I thought AWE is just for servers who break the 4GB
> boundary... Would like to know why the memory utilization don't go upper
> than
> 1,84gb, even setting this as a fixed value in Server configuration...
> Thx,
> Rafa|||Keith,
Why would you use the /PAE and AWE switches if his server only has 4 GB RAM.
Those settings are for servers with more than 4GB.
"Keith Kratochvil" wrote:
> Since you are running on Enterprise Edition you could try using /3GB and or
> /PAE within boot.ini.
> You will then probably want to specify the memory usage within SQL Server
> Using AWE Memory on Windows 2000
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_sa_6b3k.htm
> Managing AWE Memory
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\adminsql.chm::/ad_1_server_1fnd.htm
> --
> Keith
>
> "Rafa®" <Rafa@.discussions.microsoft.com> wrote in message
> news:98A36C40-7BAF-4883-902D-D01BFE02FEFB@.microsoft.com...
> > Guys,
> > I have a server running MS-SQL SP3. The server configuration is a
> > Dual-Xeon
> > 2.4Ghz, with 4GB RAM. The server is reserved for running SQL Server, so he
> > can use the whole memory for the SQL Server service...
> >
> > Just as a 2GB server that I had before, monitoring with Task Manager I see
> > that the memory utilization don't grow up more than 1,84gb... Even with
> > huge
> > processing and disk reading... So my question is, is there any kind of
> > special configuration that you must set to let server use the whole
> > memory?
> >
> > I know about AWE, but I thought AWE is just for servers who break the 4GB
> > boundary... Would like to know why the memory utilization don't go upper
> > than
> > 1,84gb, even setting this as a fixed value in Server configuration...
> >
> > Thx,
> > Rafa
>
>
memory utilization
What do people think is normal for memory utilization? I know that's too
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
TomSQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
--
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> > What do people think is normal for memory utilization? I know that's
too
> > broad, so here are some basics.
> >
> > MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> > Db 1, size = 2.0 GB
> > Db 2, size = 300MB
> > Db 3, size = 50MB
> > Db 4, size = 30MB
> > Db 5, size = 30MB
> >
> > Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
> slowed.
> >
> > Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> > Sun 61MB
> > Mon 200MB
> > Tues 800MB
> > Wed 1,124MB
> > Thu 1,424MB
> > Fri 1,303MB
> >
> > I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> > unable to allocate from the system paged pool because the pool was
empty."
> > Then I did several updates to address this and got more RAM. I haven't
> seen
> > the errors since, but I haven't waited for them to happen: I'm rebooting
> > every week now. The memory numbers make me suspect SQL Server.
> >
> > Scratching my head. Not sure if my problem is gone, and this is normal
> SQL
> > Server 2000 behavior, or if my problem is still lurking and I've only
> muted
> > it a bit.
> >
> > Any thoughts greatly appreciated.
> >
> > Tom
> >
> >
> >
>sql
broad, so here are some basics.
MS SQL Server 2000, Windows 2000 Server, 2GB RAM
Db 1, size = 2.0 GB
Db 2, size = 300MB
Db 3, size = 50MB
Db 4, size = 30MB
Db 5, size = 30MB
Typically 4-6 users, moderate usage 8-hrs/day. Performance has not slowed.
Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
Sun 61MB
Mon 200MB
Tues 800MB
Wed 1,124MB
Thu 1,424MB
Fri 1,303MB
I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
unable to allocate from the system paged pool because the pool was empty."
Then I did several updates to address this and got more RAM. I haven't seen
the errors since, but I haven't waited for them to happen: I'm rebooting
every week now. The memory numbers make me suspect SQL Server.
Scratching my head. Not sure if my problem is gone, and this is normal SQL
Server 2000 behavior, or if my problem is still lurking and I've only muted
it a bit.
Any thoughts greatly appreciated.
TomSQL Server will use all the ram that it thinks it can up to it's max. From
there it will dynamically allocate as it sees fit but it will not release
any back to the OS unless it specifically calls for it. So your behavior
does not seem uncommon. I would hold off rebooting and see if it happens
again. If you are running other apps on the same server you may still see
some completion for ram but you should not starve it.
--
Andrew J. Kelly SQL MVP
"Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> What do people think is normal for memory utilization? I know that's too
> broad, so here are some basics.
> MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> Db 1, size = 2.0 GB
> Db 2, size = 300MB
> Db 3, size = 50MB
> Db 4, size = 30MB
> Db 5, size = 30MB
> Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
slowed.
> Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> Sun 61MB
> Mon 200MB
> Tues 800MB
> Wed 1,124MB
> Thu 1,424MB
> Fri 1,303MB
> I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> unable to allocate from the system paged pool because the pool was empty."
> Then I did several updates to address this and got more RAM. I haven't
seen
> the errors since, but I haven't waited for them to happen: I'm rebooting
> every week now. The memory numbers make me suspect SQL Server.
> Scratching my head. Not sure if my problem is gone, and this is normal
SQL
> Server 2000 behavior, or if my problem is still lurking and I've only
muted
> it a bit.
> Any thoughts greatly appreciated.
> Tom
>
>|||This makes sense. I'll take a couple pills, hold off rebooting and see if
it behaves properly.
Thanks for the suggestion.
Tom
"Andrew J. Kelly" <sqlmvpnoooospam@.shadhawk.com> wrote in message
news:e7YZdiHPEHA.2876@.TK2MSFTNGP09.phx.gbl...
> SQL Server will use all the ram that it thinks it can up to it's max.
From
> there it will dynamically allocate as it sees fit but it will not release
> any back to the OS unless it specifically calls for it. So your behavior
> does not seem uncommon. I would hold off rebooting and see if it happens
> again. If you are running other apps on the same server you may still see
> some completion for ram but you should not starve it.
> --
> Andrew J. Kelly SQL MVP
>
> "Thomas Moy" <tomoy64@.myprivacy.ca> wrote in message
> news:cbqdnRae09adgzTd4p2dnA@.giganews.com...
> > What do people think is normal for memory utilization? I know that's
too
> > broad, so here are some basics.
> >
> > MS SQL Server 2000, Windows 2000 Server, 2GB RAM
> > Db 1, size = 2.0 GB
> > Db 2, size = 300MB
> > Db 3, size = 50MB
> > Db 4, size = 30MB
> > Db 5, size = 30MB
> >
> > Typically 4-6 users, moderate usage 8-hrs/day. Performance has not
> slowed.
> >
> > Reboot on Sunday. sqlservr.exe in the Task Manager reports the following
> > Sun 61MB
> > Mon 200MB
> > Tues 800MB
> > Wed 1,124MB
> > Thu 1,424MB
> > Fri 1,303MB
> >
> > I was getting srv 2020 errors when I had just 1 GB RAM: "The server was
> > unable to allocate from the system paged pool because the pool was
empty."
> > Then I did several updates to address this and got more RAM. I haven't
> seen
> > the errors since, but I haven't waited for them to happen: I'm rebooting
> > every week now. The memory numbers make me suspect SQL Server.
> >
> > Scratching my head. Not sure if my problem is gone, and this is normal
> SQL
> > Server 2000 behavior, or if my problem is still lurking and I've only
> muted
> > it a bit.
> >
> > Any thoughts greatly appreciated.
> >
> > Tom
> >
> >
> >
>sql
memory used by sqlservr
Hi,
My sql server is running on a Windows 2000 server with 2G physical memory
machine and I'm looking at the private-bytes performance counter for
sqlservr process and it's taking 1.8G. Is that something I should be
concerned about? I assume that sqlserver can be smart in taking most
possible available memory - so that would explain it. But how do I know when
I should be concerned - in the case 1.8 is the actual minimum it needs to
run efficiently (constantly swapping memory with page file is not efficient
of course).
In another word, how do I know when to start investing in more hardware for
my sql server?
thanks!Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
http://www.mssqlserver.com/faq/trou...-memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Zen" <zen@.nononospam.com> wrote in message news:uolOKk9YGHA.4688@.TK2MSFTNGP04.phx.gbl...[vb
col=seagreen]
> Hi,
> My sql server is running on a Windows 2000 server with 2G physical memory
> machine and I'm looking at the private-bytes performance counter for
> sqlservr process and it's taking 1.8G. Is that something I should be
> concerned about? I assume that sqlserver can be smart in taking most
> possible available memory - so that would explain it. But how do I know wh
en
> I should be concerned - in the case 1.8 is the actual minimum it needs to
> run efficiently (constantly swapping memory with page file is not efficien
t
> of course).
> In another word, how do I know when to start investing in more hardware fo
r
> my sql server?
> thanks!
>[/vbcol]
My sql server is running on a Windows 2000 server with 2G physical memory
machine and I'm looking at the private-bytes performance counter for
sqlservr process and it's taking 1.8G. Is that something I should be
concerned about? I assume that sqlserver can be smart in taking most
possible available memory - so that would explain it. But how do I know when
I should be concerned - in the case 1.8 is the actual minimum it needs to
run efficiently (constantly swapping memory with page file is not efficient
of course).
In another word, how do I know when to start investing in more hardware for
my sql server?
thanks!Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/defaul...b;en-us;q321363
http://www.mssqlserver.com/faq/trou...-memoryleak.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Zen" <zen@.nononospam.com> wrote in message news:uolOKk9YGHA.4688@.TK2MSFTNGP04.phx.gbl...[vb
col=seagreen]
> Hi,
> My sql server is running on a Windows 2000 server with 2G physical memory
> machine and I'm looking at the private-bytes performance counter for
> sqlservr process and it's taking 1.8G. Is that something I should be
> concerned about? I assume that sqlserver can be smart in taking most
> possible available memory - so that would explain it. But how do I know wh
en
> I should be concerned - in the case 1.8 is the actual minimum it needs to
> run efficiently (constantly swapping memory with page file is not efficien
t
> of course).
> In another word, how do I know when to start investing in more hardware fo
r
> my sql server?
> thanks!
>[/vbcol]
memory used by sqlservr
Hi,
My sql server is running on a Windows 2000 server with 2G physical memory
machine and I'm looking at the private-bytes performance counter for
sqlservr process and it's taking 1.8G. Is that something I should be
concerned about? I assume that sqlserver can be smart in taking most
possible available memory - so that would explain it. But how do I know when
I should be concerned - in the case 1.8 is the actual minimum it needs to
run efficiently (constantly swapping memory with page file is not efficient
of course).
In another word, how do I know when to start investing in more hardware for
my sql server?
thanks!Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Zen" <zen@.nononospam.com> wrote in message news:uolOKk9YGHA.4688@.TK2MSFTNGP04.phx.gbl...
> Hi,
> My sql server is running on a Windows 2000 server with 2G physical memory
> machine and I'm looking at the private-bytes performance counter for
> sqlservr process and it's taking 1.8G. Is that something I should be
> concerned about? I assume that sqlserver can be smart in taking most
> possible available memory - so that would explain it. But how do I know when
> I should be concerned - in the case 1.8 is the actual minimum it needs to
> run efficiently (constantly swapping memory with page file is not efficient
> of course).
> In another word, how do I know when to start investing in more hardware for
> my sql server?
> thanks!
>
My sql server is running on a Windows 2000 server with 2G physical memory
machine and I'm looking at the private-bytes performance counter for
sqlservr process and it's taking 1.8G. Is that something I should be
concerned about? I assume that sqlserver can be smart in taking most
possible available memory - so that would explain it. But how do I know when
I should be concerned - in the case 1.8 is the actual minimum it needs to
run efficiently (constantly swapping memory with page file is not efficient
of course).
In another word, how do I know when to start investing in more hardware for
my sql server?
thanks!Have a look at
INF: SQL Server Memory Usage
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321363
http://www.mssqlserver.com/faq/troubleshooting-memoryleak.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Zen" <zen@.nononospam.com> wrote in message news:uolOKk9YGHA.4688@.TK2MSFTNGP04.phx.gbl...
> Hi,
> My sql server is running on a Windows 2000 server with 2G physical memory
> machine and I'm looking at the private-bytes performance counter for
> sqlservr process and it's taking 1.8G. Is that something I should be
> concerned about? I assume that sqlserver can be smart in taking most
> possible available memory - so that would explain it. But how do I know when
> I should be concerned - in the case 1.8 is the actual minimum it needs to
> run efficiently (constantly swapping memory with page file is not efficient
> of course).
> In another word, how do I know when to start investing in more hardware for
> my sql server?
> thanks!
>
Subscribe to:
Posts (Atom)