Monday, March 19, 2012
Memory Usage On SQL 2K
showing well over 7GB in use but the processes do not add up to near that
amount. How can I determine what is grabbing all the memory on this server?
Thanks, Sean
Duplicate Post
"Sean" wrote:
> I have SQL 2000 running with 8GG of RAM and 8 procs. In Task Manager it is
> showing well over 7GB in use but the processes do not add up to near that
> amount. How can I determine what is grabbing all the memory on this server?
> Thanks, Sean
Memory Usage On SQL 2K
showing well over 7GB in use but the processes do not add up to near that
amount. How can I determine what is grabbing all the memory on this server?
Thanks, SeanDuplicate Post
"Sean" wrote:
> I have SQL 2000 running with 8GG of RAM and 8 procs. In Task Manager it i
s
> showing well over 7GB in use but the processes do not add up to near that
> amount. How can I determine what is grabbing all the memory on this serve
r?
> Thanks, Sean
Memory Usage On SQL 2K
showing well over 7GB in use but the processes do not add up to near that
amount. How can I determine what is grabbing all the memory on this server?
Thanks, SeanDuplicate Post
"Sean" wrote:
> I have SQL 2000 running with 8GG of RAM and 8 procs. In Task Manager it is
> showing well over 7GB in use but the processes do not add up to near that
> amount. How can I determine what is grabbing all the memory on this server?
> Thanks, Sean
Memory Usage on SQL 2000
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
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 usage in SQL Server
How can I tell how much memory SQL Server is using on a server. On
Windows 2000, whenever I go to Task manager/processes/memory usage SQL
Server seems to be showing 1,744,124K. On all of my servers with
various size, usage of databases, all of them show SQL Server to be
using about the same amount of memory. Can someone explain this to me?
Shouldn't it use more for larger databases, heavy hitting databases?
Also, I normally check Dynamically configure SQL Server memory and put
the maximum threshold to a little bit less than the max on the server.
The minimum query memory is set to 1024. Is that 1024 a subset of the
memory used by SQL Server, or is this additional that can be used?
Thanks,
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***Raziq Shekha (raziq_shekha@.anadarko.com) writes:
> How can I tell how much memory SQL Server is using on a server. On
> Windows 2000, whenever I go to Task manager/processes/memory usage SQL
> Server seems to be showing 1,744,124K. On all of my servers with
> various size, usage of databases, all of them show SQL Server to be
> using about the same amount of memory. Can someone explain this to me?
> Shouldn't it use more for larger databases, heavy hitting databases?
So how much memory is available on these boxes? Which edition of SQL
Server are they running?
SQL Server is designed to grab as much memory there is available, so if
these servers have 2GB of memory, it is very likely that all servers
by time reach this level. (The rest is left to the Operating System.(
> Also, I normally check Dynamically configure SQL Server memory and put
> the maximum threshold to a little bit less than the max on the server.
Actually, there is no reason to set any limit at all, unless there
are other apps on the machine. If you do this setting, add more memory,
and forget the setting, the new memory will not be used.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||These boxes have about 4 gigs of memory total. They are running SQL
2000 SP3. But all servers regardless of activity and size or number of
databases are showing as SQL Server using the same amount of memory.
*** Sent via Developersdex http://www.developersdex.com ***|||Raziq Shekha (raziq_shekha@.anadarko.com) writes:
> These boxes have about 4 gigs of memory total. They are running SQL
> 2000 SP3. But all servers regardless of activity and size or number of
> databases are showing as SQL Server using the same amount of memory.
And which edition? Standard Editoin cannot acceess more than 2GB of
memory, as I recall.
Enterrise Manager can access more, but you need to use the /AWE, /PAE
or /3GB switches in your Boot.ini. I don't this sort of memory configuration
myself, but search for this in Knowledge Base, and you should find some
useful information.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns96C463036A89Yazorman@.127.0.0.1...
> Raziq Shekha (raziq_shekha@.anadarko.com) writes:
> > These boxes have about 4 gigs of memory total. They are running SQL
> > 2000 SP3. But all servers regardless of activity and size or number of
> > databases are showing as SQL Server using the same amount of memory.
> And which edition? Standard Editoin cannot acceess more than 2GB of
> memory, as I recall.
Correct. And 1.7 is in the ballpark of a maxed out server from what we
have.
> Enterrise Manager can access more, but you need to use the /AWE, /PAE
Err, I think you mean the Enterprise Version. And I believe this is only
Advanced Server 2000 (or if you use certain versions of 2003)
> or /3GB switches in your Boot.ini. I don't this sort of memory
configuration
> myself, but search for this in Knowledge Base, and you should find some
> useful information.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||It is Enterprise Edition. So why are all my enterprise editions showing
SQL using 1.7gigs of memory when there is quite more available. And why
are all of them using the same amount? Some have more activity than
others, some have larger databases than others. But all of them are
using the same amount of memory? Por Que?
*** Sent via Developersdex http://www.developersdex.com ***|||It is Enterprise Edition. So why are all my enterprise editions showing
SQL using 1.7gigs of memory when there is quite more available. And why
are all of them using the same amount? Some have more activity than
others, some have larger databases than others. But all of them are
using the same amount of memory? Por Que?
*** Sent via Developersdex http://www.developersdex.com ***|||Raziq Shekha (raziq_shekha@.anadarko.com) writes:
> It is Enterprise Edition. So why are all my enterprise editions showing
> SQL using 1.7gigs of memory when there is quite more available. And why
> are all of them using the same amount? Some have more activity than
> others, some have larger databases than others. But all of them are
> using the same amount of memory? Por Que?
I suggested last night that you search Knowledge Base, as I was just
off to bed. Apparently, you prefer to someone else do that work for you,
so I performed this search:
http://support.microsoft.com/search...&mode=a&x=0&y=0
This article looks like the best start:
http://support.microsoft.com/defaul...kb;en-us;274750.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:jcHRe.53$ON3.4168@.news.uswest.net...
> It is Enterprise Edition. So why are all my enterprise editions showing
> SQL using 1.7gigs of memory when there is quite more available. And why
> are all of them using the same amount? Some have more activity than
> others, some have larger databases than others. But all of them are
> using the same amount of memory? Por Que?
>
> *** Sent via Developersdex http://www.developersdex.com ***
As Erland has already explained, SQL Server doesn't release memory once it
has grabbed it. Thus it doesn't take it long to grab memory up to any limit
that might be set. My guess is that if you open enterprise manager, and go
to server properties and look on the memory tab, that sql server has been
configured to use up to about 1.7gb.
Brian.
--
www.cryer.co.uk/brian|||That is not the case. My SQL Servers have been configured to use more
than 1.7G of memory. But they are all using the same amount 1.7G.
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***
Monday, March 12, 2012
memory usage - pages or KB?
It's (8 KB) pages. See the documentation for sysprocesses (from which the
information in Enterprise Manager is derived) in BOL.
Where did you read the information that it was KB instead of pages btw?
Jacco Schalkwijk
SQL Server MVP
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:37D533A5-479A-48E6-A12A-7CF2E83883FB@.microsoft.com...
>I have read conflicting reports that the number in the memory usage column
>under Current Processes is the number of pages and that it is the number of
>KB of allocated memory. Which one is correct? Thanks
|||A couple of people had told me that, and one of them referenced this page:
http://www.microsoft.com/technet/pro.../c03ppcsq.mspx
but more sources say it is the number of pages so I will stick with that. Thanks.
"Jacco Schalkwijk" wrote:
> It's (8 KB) pages. See the documentation for sysprocesses (from which the
> information in Enterprise Manager is derived) in BOL.
> Where did you read the information that it was KB instead of pages btw?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
> news:37D533A5-479A-48E6-A12A-7CF2E83883FB@.microsoft.com...
>
>
memory usage - pages or KB?
nder Current Processes is the number of pages and that it is the number of K
B of allocated memory. Which one is correct? ThanksIt's (8 KB) pages. See the documentation for sysprocesses (from which the
information in Enterprise Manager is derived) in BOL.
Where did you read the information that it was KB instead of pages btw?
Jacco Schalkwijk
SQL Server MVP
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:37D533A5-479A-48E6-A12A-7CF2E83883FB@.microsoft.com...
>I have read conflicting reports that the number in the memory usage column
>under Current Processes is the number of pages and that it is the number of
>KB of allocated memory. Which one is correct? Thanks|||A couple of people had told me that, and one of them referenced this page:
http://www.microsoft.com/technet/pr...s/c03ppcsq.mspx
but more sources say it is the number of pages so I will stick with that. Th
anks.
"Jacco Schalkwijk" wrote:
> It's (8 KB) pages. See the documentation for sysprocesses (from which the
> information in Enterprise Manager is derived) in BOL.
> Where did you read the information that it was KB instead of pages btw?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
> news:37D533A5-479A-48E6-A12A-7CF2E83883FB@.microsoft.com...
>
>
Friday, February 24, 2012
Memory Paging
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?
The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
Memory Paging
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have t
o
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?
Memory Paging
that is almost constantly paging OS processes (>500pg/sec 6-10 times an
hour).
Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major paging
culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have to
have the MOM stuff on there.
What are the other 2, and do they need to be running on a box dedicated to
SQL?
Any other ideas for helping me lower my paging rate?The paging is really not that excessive. But in order to reduce paging you
need to ensure there is always enough memory for the apps other than SQL
Server as well as the OS. So 2GB might not be enough to satisfy these other
apps. I don't know how much MOM requires but I am suppressed the 2GB is not
enough for these.
--
Andrew J. Kelly SQL MVP
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?|||wmiprvse is a process that is an instance of a wmi provider
(there are some trojans/worms that hide in this proccess also)
but it is more likely mom is using this provider.
RemoteRegistry does what its name implies, it lets users access the registry
remotely....it is a service which CAN be disabled...but i dont know about
moms dependencies on this either.
"Budman" <Budman@.discussions.microsoft.com> wrote in message
news:F55C30B9-B696-4303-8FF4-F9B51E0F49FF@.microsoft.com...
>I have a SQL Server 2000 running on Windows 2003 (both Enterprise Editions)
> that is almost constantly paging OS processes (>500pg/sec 6-10 times an
> hour).
> Its a 4 proc box, and I have 10GB RAM (8 to SQL; 2 to OS). The major
> paging
> culprits are MOM Hosts and Services, wmiprvse, and RemoteRegistry. I have
> to
> have the MOM stuff on there.
> What are the other 2, and do they need to be running on a box dedicated to
> SQL?
> Any other ideas for helping me lower my paging rate?