Event 17890 in Application Event Log

Hello,
on one of my servers I'm getting Event 17890 at irregular intervals in the
event log. Since the server is running in German, I can't provide the exact
wording, but loosely translated it's more or less: "A large part of the SQL
Server process memory has been paged. This can cause performance problems."
And then there's some information on the size of the working set, the commit
and memory use in %.
I haven't seen this on any other SQL Server machine, and I can't find any
information about the event in the documentation or on the net. Is this
something to be worried about? What can I do to prevent it?
The server has 2 GB of RAM, there are a couple of SQL instances running, but
not much else. If there's any other information I can supply that would help
,
I'd be glad to.
Thanks for any suggestions.Probably 1 of youre instances needs more memory.
You can add more memory per instance in enterprisemanager.|||hi,
You should consider configuring the memory limits to each of the sql
instances, having in consideration that you should leave memory available fo
r
the OS.
Having that in mind, the first thing to do is to have an idea of how much
memory each of the sql instances need.
Paulo Ferreira
http://www.info2k.pt
SQL Server DBA Experts
"Tom Juergens" wrote:

> Hello,
> on one of my servers I'm getting Event 17890 at irregular intervals in the
> event log. Since the server is running in German, I can't provide the exac
t
> wording, but loosely translated it's more or less: "A large part of the SQ
L
> Server process memory has been paged. This can cause performance problems.
"
> And then there's some information on the size of the working set, the comm
it
> and memory use in %.
> I haven't seen this on any other SQL Server machine, and I can't find any
> information about the event in the documentation or on the net. Is this
> something to be worried about? What can I do to prevent it?
> The server has 2 GB of RAM, there are a couple of SQL instances running, b
ut
> not much else. If there's any other information I can supply that would he
lp,
> I'd be glad to.
> Thanks for any suggestions.|||Thanks,
that sounds sensible, but I must admit I'm not sure how best to go about it.
I've checked: There are 2 instances of SQL2000 and one SQL2005. They are all
using dynamic memory allocation: One instance of 2000 is set to use between
0
and 512 MB, whereas the other two use the default values of 0 and 2147483647
MB.
I can use perfmon to check the amount of memory currently used by each
instance, but that doesn't tell me how much they might need max. Plus, the
instance which is used most and has the largest database is also using the
most memory (over 1 GB), which makes sense, but this is also the instance
that is causing event 17890. So I suppose either one of the other instances
or another process is suddenly asking for more memory.
Am I on the right track? And what do I do next? Thanks for your help!
Tom
"Paulo Ferreira" wrote:
[vbcol=seagreen]
> hi,
> You should consider configuring the memory limits to each of the sql
> instances, having in consideration that you should leave memory available
for
> the OS.
> Having that in mind, the first thing to do is to have an idea of how much
> memory each of the sql instances need.
> --
> Paulo Ferreira
> http://www.info2k.pt
> SQL Server DBA Experts
>
>
> "Tom Juergens" wrote:
>|||Hello Tom,
Did you use SQL 2005 x64 version? If so, please follow this KB article
How to reduce paging of buffer pool memory in the 64-bit version of SQL
Server 2005
http://support.microsoft.com/kb/918483
If not, please let me know how many physical memory your server have?
If your SQL Server configured to use all the memory, once other application
required memory, it requested it from the OS and the OS on it turn requests
all processes on the machine to trim their working set (or the virtual
memory that is in RAM). So such a scenario caused SQL Server memory to be
trimmed and paged out to page file. When SQL memory gets paged out the
performance goes to a crawl.
My suggestion is limited the Maz Server Memory for the SQL 2005 instance
which allow some RAM for other application.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Wei Lu,
no, it's not x64, and the server has 2 GB physical memory. I guess I'll
limit the memory for this SQL instance to around 1 GB and see if that helps.
And then I can play around with the memory allocation to see if more or less
gives me better results.
That leaves me with two follow-on questions:
Is there any point in setting the minimum memory?
What's the best way to determine the max memory actually used over a period
of time, so that I can decide if I need to allocate more or less?
Thank you
Tom
"Wei Lu [MSFT]" wrote:

> Hello Tom,
> Did you use SQL 2005 x64 version? If so, please follow this KB article
> How to reduce paging of buffer pool memory in the 64-bit version of SQL
> Server 2005
> http://support.microsoft.com/kb/918483
> If not, please let me know how many physical memory your server have?
> If your SQL Server configured to use all the memory, once other applicatio
n
> required memory, it requested it from the OS and the OS on it turn request
s
> all processes on the machine to trim their working set (or the virtual
> memory that is in RAM). So such a scenario caused SQL Server memory to be
> trimmed and paged out to page file. When SQL memory gets paged out the
> performance goes to a crawl.
> My suggestion is limited the Maz Server Memory for the SQL 2005 instance
> which allow some RAM for other application.
> Hope this helps.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||Hello Tom,
You could use the perfmon to check the memory OS allocated to SQL Server.
I don't think the minimum memory will effect in this scenario.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.