|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > SQL Server 2000 Maxing Memory
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server 2000 Maxing Memory
|
|
| Mike Schinkel 2002-11-25, 4:23 pm |
| I got a SQL Server 2000 running the backend of a website, and after several
hours it starts maxing memory (I have 1Gb installed).
I restart the service, and everything goes back to normal. 12 hours later,
same problem.
Where do I start looking for answers? Thanks in advance.
-Mike
| |
|
| Under "memory/ max server memory option" in BOL.
"Mike Schinkel" <mikes@xtras.com> wrote in message
news:O6K1T$MlCHA.488@tkmsftngp02...
> I got a SQL Server 2000 running the backend of a website, and after
several
> hours it starts maxing memory (I have 1Gb installed).
> I restart the service, and everything goes back to normal. 12 hours
later,
> same problem.
>
> Where do I start looking for answers? Thanks in advance.
>
> -Mike
>
>
| |
| James Hunter Ross 2002-11-25, 5:23 pm |
| You might want to add memory. Typically, SQL Server will grab as much as it
can for use as page and procedure cache, and for locks. It attempts to
cooperate with the OS so as not to take so much as to increase paging.
Is this "taking of all the memory" causing a problem? Memory is cheap, and
SQL Server can make good use of it.
James
| |
| Mike Schinkel 2002-11-25, 6:23 pm |
| We had a lesser box running the SQL database for the website and that box
had 512kMb and was a 700 Athlon. This new box is a Dell 2500 w/1Gb w/dual
1Ghz Pentium 4s. The old box was fine, but the new box is maxing memory.
So I have to believe it is in the software config.
Don't have a problem adding memory, but I fear that may not solve the
problem.
-Mike
"James Hunter Ross" <jhr@delta.net> wrote in message
news:#mZ9mNNlCHA.3752@tkmsftngp08...
> You might want to add memory. Typically, SQL Server will grab as much as
it
> can for use as page and procedure cache, and for locks. It attempts to
> cooperate with the OS so as not to take so much as to increase paging.
>
> Is this "taking of all the memory" causing a problem? Memory is cheap,
and
> SQL Server can make good use of it.
>
> James
>
>
| |
|
| So did you try setting the max memory option? Did it work?
"Mike Schinkel" <mikes@xtras.com> wrote in message
news:#R$dOyNlCHA.1324@tkmsftngp04...
> We had a lesser box running the SQL database for the website and that box
> had 512kMb and was a 700 Athlon. This new box is a Dell 2500 w/1Gb w/dual
> 1Ghz Pentium 4s. The old box was fine, but the new box is maxing memory.
> So I have to believe it is in the software config.
>
> Don't have a problem adding memory, but I fear that may not solve the
> problem.
>
> -Mike
>
> "James Hunter Ross" <jhr@delta.net> wrote in message
> news:#mZ9mNNlCHA.3752@tkmsftngp08...
> > You might want to add memory. Typically, SQL Server will grab as much
as
> it
> > can for use as page and procedure cache, and for locks. It attempts to
> > cooperate with the OS so as not to take so much as to increase paging.
> >
> > Is this "taking of all the memory" causing a problem? Memory is cheap,
> and
> > SQL Server can make good use of it.
> >
> > James
> >
> >
>
>
| |
| Tibor Karaszi 2002-11-26, 2:23 am |
| SQL Server is designed to use the memory in the machine, if needed, so this might be just
normal.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"Mike Schinkel" <mikes@xtras.com> wrote in message news:O6K1T$MlCHA.488@tkmsftngp02...
> I got a SQL Server 2000 running the backend of a website, and after several
> hours it starts maxing memory (I have 1Gb installed).
> I restart the service, and everything goes back to normal. 12 hours later,
> same problem.
>
> Where do I start looking for answers? Thanks in advance.
>
> -Mike
>
>
| |
| Greg D. Moore \(Strider\) 2002-11-28, 9:24 am |
|
"Mike Schinkel" <mikes@xtras.com> wrote in message
news:O6K1T$MlCHA.488@tkmsftngp02...
> I got a SQL Server 2000 running the backend of a website, and after
several
> hours it starts maxing memory (I have 1Gb installed).
> I restart the service, and everything goes back to normal. 12 hours
later,
> same problem.
Not to be facetious, but "is this really a problem?"
Seriously, normally you WANT SQL Server to use as much memory as possible.
It can cache more and be more effecient that way.
So unless this is causing other problems, I wouldn't worry.
>
> Where do I start looking for answers? Thanks in advance.
>
> -Mike
>
>
| |
| Brad Wartman 2002-11-30, 8:23 am |
| Unless you specify otherwise, SQL Server will use up to 2 GB of RAM
for its operations with 4 GB of total memory (2 GB for the OS and 2 GB
for SQL Server) total (the max addressable space for a 32-bit OS).
If you're using the Enterprise Edition, you can reallocate the memory
split to 1 GB for OS and 3 GB for SQL Server by adding the /3GB
switch to your boot.ini file (see BOL on "AWE" for more info). If
you're running Win2K Advanced Server or Data Center you can address up
to either 8 or 64 GB respectively with Enterprise Edition.
I suggest you look at adding more memory to your server anyway. With
only 1 GB for both your OS and SQL Server, there's got to be a lot of
swapping going on and that'll have a dramatic effect on SQL Server
performance. I recommend you install at least 1 GB and up to 3 GB more
if at all possible. SQL Server uses the extra memory for its caching
and chances are good that for the few $ the extra memory costs you'll
see a hefty gain in performance.
On Thu, 28 Nov 2002 14:54:24 GMT, "Greg D. Moore \(Strider\)"
<mooregr@greenms.com> wrote:
>
>"Mike Schinkel" <mikes@xtras.com> wrote in message
>news:O6K1T$MlCHA.488@tkmsftngp02...
>> I got a SQL Server 2000 running the backend of a website, and after
>several
>> hours it starts maxing memory (I have 1Gb installed).
>> I restart the service, and everything goes back to normal. 12 hours
>later,
>> same problem.
>
>Not to be facetious, but "is this really a problem?"
>
>Seriously, normally you WANT SQL Server to use as much memory as possible.
>It can cache more and be more effecient that way.
>
>So unless this is causing other problems, I wouldn't worry.
>
>
>>
>> Where do I start looking for answers? Thanks in advance.
>>
>> -Mike
>>
>>
>
|
|
|
|
|