Re: How to tell how much memory is actually needed by my SQL Server 2000??
From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 10/27/04
- Next message: Dejan Sarka: "Re: Stored procedures security"
- Previous message: Steve H: "Left Outer Join and CONTAINS - performance question..."
- In reply to: Peter The Spate: "How to tell how much memory is actually needed by my SQL Server 2000??"
- Next in thread: Peter The Spate: "Re: How to tell how much memory is actually needed by my SQL Server 2000??"
- Reply: Peter The Spate: "Re: How to tell how much memory is actually needed by my SQL Server 2000??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 27 Oct 2004 08:19:27 -0500
I don't know if that method will work.
We are running SQL 2k EE on Win2k AS. We are using /3GB /PAE and SQL Server
is configured to use 6144 MB.
Task manager reports that sqlservr.exe is using 115,524K on the process tab
however on the performance tab the physical memory is reported as
Total 7863624
Available 1184100
-- Keith "Peter The Spate" <anonymous@discussions.microsoft.com> wrote in message news:15d501c4bc26$57a92ae0$a601280a@phx.gbl... > The easiest way of doing it is to go onto your server, > doing a CTR ALT DEL, bringing up task manager, then > looking for SQL Server under the processors list. > > Peter > > "I'm just preparing my impromptu remarks." > Winston Churchill > > > > >-----Original Message----- > >I've been doing a lot of reading on this and my head is > starting to > >hurt! It seems to be quite a feat to work out how much > memory is > >actually being used by our server. > > > >I'm running W2K advanced server with SQL 2000 EE, 8GB of > RAM, a min of > >4GB and a max of 6GB is assigned to SQL server. > > > >I'm trying to work out whether we've assigned enough or > too > >much/little memory to SQL server. My first thought was to > let SQL > >dymanically manage its own memory and see how much it > uses, of course > >when AWE (/3GB /PAE) is enabled it will just use all that > is > >available. > > > >In perfmon "target server memory" = 6.1GB, "total server > memory" = > >6.1GB, "total pages" = 768000 ( x 8KB = 6.1GB). > > > >My second thought was to use "total pages" - the > average "free pages" > >= average mem used, therefore giving me the average > amount of memory > >used by SQL. I found out that SQL uses a min of 4GB (the > min we > >assigned) and the max of all the memory, 6GB. > > > >Is there an easier way of finding out how much memory is > actually used > >in this situation or is going by the above average the > best way? > > > >What i'm unsure about is if, for example, we made 1TB of > RAM > >available, will SQL just use all memory assigned to it > until it has > >the whole DB in memory? If not, what's the cut off? Or is > the fact > >that the memory usage of our instance of sql peaks at > using all the > >memory an indication that we do not have enough available? > > > >Any help would be greatly apprechiated. > > > >Thanks. > >. > >
- Next message: Dejan Sarka: "Re: Stored procedures security"
- Previous message: Steve H: "Left Outer Join and CONTAINS - performance question..."
- In reply to: Peter The Spate: "How to tell how much memory is actually needed by my SQL Server 2000??"
- Next in thread: Peter The Spate: "Re: How to tell how much memory is actually needed by my SQL Server 2000??"
- Reply: Peter The Spate: "Re: How to tell how much memory is actually needed by my SQL Server 2000??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
