Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this server?
Thanks, SeanHi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:
> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use in
> Task Manager is showing over 7GB in use but the processes in Task Manager do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this server?
> Thanks, Sean

Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this server?
Thanks, Sean
Hi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:

> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use in
> Task Manager is showing over 7GB in use but the processes in Task Manager do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this server?
> Thanks, Sean

Memory Usage on SQL 2000

Good Morning All,
I have a SQL server with 8GB of memory and 8 processors. The memory use in
Task Manager is showing over 7GB in use but the processes in Task Manager do
not add up to anywhere near that amount of RAM being used.
My question is how do I determine what is using all of the RAM on this serve
r?
Thanks, SeanHi
Once you use PAE or AWE, task manager does not show the memory correctly.
You need to look at the Performance Counters presented in the OS perfmon
utility.
The see what is configured for SQL run the following in QA:
sp_configure 'show advanced options', 1
sp_configure 'awe enabled'
sp_configure 'min server memory'
sp_configure 'max server memory'
Regards
Mike
"Sean" wrote:

> Good Morning All,
> I have a SQL server with 8GB of memory and 8 processors. The memory use i
n
> Task Manager is showing over 7GB in use but the processes in Task Manager
do
> not add up to anywhere near that amount of RAM being used.
> My question is how do I determine what is using all of the RAM on this ser
ver?
> Thanks, Sean

Memory Settings

Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
RAM on the box. 3 questions for the experts:
(1) Firstly, my understanding is that only 4GB can be used by windows - is
this correct?
(2) do we still have to change boot.ini file or is this not needed with
windows 2003?
(3) do we need to make changes to sp_configure - the max server memory will
need changing but how about the AWE setting?
Thanks.Jack
- Enabling Memory Support for Over 4GB of Physical Memory
http://msdn2.microsoft.com/en-us/library/ms179301.aspx
"Jack" <jack@.Nospam.com> wrote in message
news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
> 8GB RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory
> will need changing but how about the AWE setting?
> Thanks.
>|||Also
http://blogs.msdn.com/slavao/
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:upLFsNjDHHA.4404@.TK2MSFTNGP06.phx.gbl...
> Jack
> - Enabling Memory Support for Over 4GB of Physical Memory
> http://msdn2.microsoft.com/en-us/library/ms179301.aspx
>
>
> "Jack" <jack@.Nospam.com> wrote in message
> news:%2367lbLjDHHA.3492@.TK2MSFTNGP02.phx.gbl...
>> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with
>> 8GB RAM on the box. 3 questions for the experts:
>> (1) Firstly, my understanding is that only 4GB can be used by windows -
>> is this correct?
>> (2) do we still have to change boot.ini file or is this not needed with
>> windows 2003?
>> (3) do we need to make changes to sp_configure - the max server memory
>> will need changing but how about the AWE setting?
>> Thanks.
>|||Hi Jack,
I just started playing with AWE my self and this is what I found so far.
SQL Server 2005 can make use of the extra memory with modifying the boot.ini.
Make sure that the account that the sql service is running as is part of the
lock pages in memory group policy, AWE is enabled in SQL server, and
configure max memory in SQL server to be at most 7GB, leaving 1 GB for the
OS. If you go to 16 GB of RAM then leave 2 GB free for the OS. The max that
the OS can use depends on the version of the OS that you are running I think.
--
MG
"Jack" wrote:
> Hi - we have SQL Server Enterprise 2005 and Windows Standard 2003, with 8GB
> RAM on the box. 3 questions for the experts:
> (1) Firstly, my understanding is that only 4GB can be used by windows - is
> this correct?
> (2) do we still have to change boot.ini file or is this not needed with
> windows 2003?
> (3) do we need to make changes to sp_configure - the max server memory will
> need changing but how about the AWE setting?
> Thanks.
>
>

memory probelm

Hi,
I have a production SQL server with 4-cpu, 8GB runs under SQL Server
Enterprise Edition & Windows 2000 Advance server.
AWE is enabled.
Max memory set to 7GB.
When I look at the Task Manager the 'Mem usage' is only 110,632 k.
Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
I am thinking there may be memory leak in the server.
My question is,
1. How can I find out if it is memory leak?
2. How to identify the process causing it?
Thanks for the help.
-sarav
Task manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>
|||Moreover, make sure you set BOTH the /3GB and /PAE switches in the BOOT.ini
file.
The /PAE switch is required by the OS in order to manage memory allocations
above 4GB. It does this by replacing the normal 32-bit address register
with a make-shift 36-bit register; thus, allowing applications written on
the extended API calls to address up to 64 GB of memory.
The /3GB switch forces the OS to reserve only 1GB for private (kernel)
addresses and 3GB for user addresses. Doing this will give you up to a 3GB
Buffer/Proc Cache instead of the default 2GB. This will give you an AWE
address space of only 4GB instead of 5GB, which would be better optimized.
Sincerely,
Anthony Thomas

"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uoL31iAAFHA.1400@.TK2MSFTNGP11.phx.gbl...
Task manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>

memory probelm

Hi,
I have a production SQL server with 4-cpu, 8GB runs under SQL Server
Enterprise Edition & Windows 2000 Advance server.
AWE is enabled.
Max memory set to 7GB.
When I look at the Task Manager the 'Mem usage' is only 110,632 k.
Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
I am thinking there may be memory leak in the server.
My question is,
1. How can I find out if it is memory leak?
2. How to identify the process causing it?
Thanks for the help.
-saravTask manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>|||Moreover, make sure you set BOTH the /3GB and /PAE switches in the BOOT.ini
file.
The /PAE switch is required by the OS in order to manage memory allocations
above 4GB. It does this by replacing the normal 32-bit address register
with a make-shift 36-bit register; thus, allowing applications written on
the extended API calls to address up to 64 GB of memory.
The /3GB switch forces the OS to reserve only 1GB for private (kernel)
addresses and 3GB for user addresses. Doing this will give you up to a 3GB
Buffer/Proc Cache instead of the default 2GB. This will give you an AWE
address space of only 4GB instead of 5GB, which would be better optimized.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uoL31iAAFHA.1400@.TK2MSFTNGP11.phx.gbl...
Task manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>

memory probelm

Hi,
I have a production SQL server with 4-cpu, 8GB runs under SQL Server
Enterprise Edition & Windows 2000 Advance server.
AWE is enabled.
Max memory set to 7GB.
When I look at the Task Manager the 'Mem usage' is only 110,632 k.
Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
I am thinking there may be memory leak in the server.
My question is,
1. How can I find out if it is memory leak?
2. How to identify the process causing it?
Thanks for the help.
-saravTask manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
--
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>|||Moreover, make sure you set BOTH the /3GB and /PAE switches in the BOOT.ini
file.
The /PAE switch is required by the OS in order to manage memory allocations
above 4GB. It does this by replacing the normal 32-bit address register
with a make-shift 36-bit register; thus, allowing applications written on
the extended API calls to address up to 64 GB of memory.
The /3GB switch forces the OS to reserve only 1GB for private (kernel)
addresses and 3GB for user addresses. Doing this will give you up to a 3GB
Buffer/Proc Cache instead of the default 2GB. This will give you an AWE
address space of only 4GB instead of 5GB, which would be better optimized.
Sincerely,
Anthony Thomas
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uoL31iAAFHA.1400@.TK2MSFTNGP11.phx.gbl...
Task manager is not the correct tool for monitoring memory usage with sql
server. Use perfmon counters instead. But when you use AWE memory Sql
Server will grab all 7GB right off the bat and will no longer dynamically
manage it.
--
Andrew J. Kelly SQL MVP
"sarav" <orumurai@.yahoo.cmom> wrote in message
news:%23XFFSaAAFHA.612@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a production SQL server with 4-cpu, 8GB runs under SQL Server
> Enterprise Edition & Windows 2000 Advance server.
> AWE is enabled.
> Max memory set to 7GB.
> When I look at the Task Manager the 'Mem usage' is only 110,632 k.
> Some of the SQL jobs run time went up from 1:30 min. to 6Hrs.
> I am thinking there may be memory leak in the server.
> My question is,
> 1. How can I find out if it is memory leak?
> 2. How to identify the process causing it?
> Thanks for the help.
> -sarav
>
>
>
>
>