A significant part of sql server process memory has been paged out.

A significant part of sql server process memory has been paged out.
This may result in a performance degradation. Duration: 0 seconds.
Working set (KB): 349620, committed (KB): 686376, memory utilization:
50%.
Has anyone been able to solve this problem on SQL Server Std Edition ?
I know the OS is trimming the Memory but apparently I have been
unable to find a way for this to stop.
"lock pages in memory" is disregarded in Std Edition.
Any thoughts ?Add RAM to the box (or if there is more than 686 MB, increasing the amount
of money allocated to SQL Server)?
Lighten the workload?
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
<isyourfriend@.gmail.com> wrote in message
news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
>A significant part of sql server process memory has been paged out.
> This may result in a performance degradation. Duration: 0 seconds.
> Working set (KB): 349620, committed (KB): 686376, memory utilization:
> 50%.
> Has anyone been able to solve this problem on SQL Server Std Edition ?
> I know the OS is trimming the Memory but apparently I have been
> unable to find a way for this to stop.
> "lock pages in memory" is disregarded in Std Edition.
> Any thoughts ?
>|||You need to know what is causing the memory shortage.
If it is the OS that really needs the memory then you probably want to
place a limit on SQL Server so that the max memory it uses leaves
enough for the OS. Starving the OS for memory guarantees poor
performance.
If there is some other application causing the memory shortage you
probably want to see if that application can be controlled.
Roy Harvey
Beacon Falls, CT
On Mon, 02 Jul 2007 15:38:01 -0000, isyourfriend@.gmail.com wrote:
>A significant part of sql server process memory has been paged out.
>This may result in a performance degradation. Duration: 0 seconds.
>Working set (KB): 349620, committed (KB): 686376, memory utilization:
>50%.
>Has anyone been able to solve this problem on SQL Server Std Edition ?
>I know the OS is trimming the Memory but apparently I have been
>unable to find a way for this to stop.
>"lock pages in memory" is disregarded in Std Edition.
>Any thoughts ?|||Are other processes running on the server? This is suboptimal.
How much RAM total? If < max allowed, add ram.
Make sure your drivers and OS and sql server are fully patched. There are
numerous known bugs in the wild that will flush ram.
--
TheSQLGuru
President
Indicium Resources, Inc.
<isyourfriend@.gmail.com> wrote in message
news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
>A significant part of sql server process memory has been paged out.
> This may result in a performance degradation. Duration: 0 seconds.
> Working set (KB): 349620, committed (KB): 686376, memory utilization:
> 50%.
> Has anyone been able to solve this problem on SQL Server Std Edition ?
> I know the OS is trimming the Memory but apparently I have been
> unable to find a way for this to stop.
> "lock pages in memory" is disregarded in Std Edition.
> Any thoughts ?
>|||On Jul 2, 11:57 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> Are other processes running on theserver? This is suboptimal.
> How much RAM total? If < max allowed, add ram.
> Make sure your drivers and OS andsqlserverare fully patched. There are
> numerous known bugs in the wild that will flush ram.
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <isyourfri...@.gmail.com> wrote in message
> news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
> >Asignificantpartofsqlserverprocessmemoryhas been paged out.
> > This may result in a performance degradation. Duration: 0 seconds.
> > Working set (KB): 349620, committed (KB): 686376,memoryutilization:
> > 50%.
> > Has anyone been able to solve this problem onSQLServerStd Edition ?
> > I know the OS is trimming theMemorybut apparently I have been
> > unable to find a way for this to stop.
> > "lock pages inmemory" is disregarded in Std Edition.
> > Any thoughts ?
The Box has 12GB of RAM.
SQL Server max memory is set to 8GB.
Windows is patched to SP2.
I am copying though "very large" backup files (around 70~100GB ) from
and to the box.
Is there *anything* I can do?|||On Jul 5, 9:19 am, isyourfri...@.gmail.com wrote:
> On Jul 2, 11:57 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
>
> > Are other processes running on theserver? This is suboptimal.
> > How much RAM total? If < max allowed, add ram.
> > Make sure your drivers and OS andsqlserverare fully patched. There are
> > numerous known bugs in the wild that will flush ram.
> > --
> > TheSQLGuru
> > President
> > Indicium Resources, Inc.
> > <isyourfri...@.gmail.com> wrote in message
> >news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
> > >Asignificantpartofsqlserverprocessmemoryhas been paged out.
> > > This may result in a performance degradation. Duration: 0 seconds.
> > > Working set (KB): 349620, committed (KB): 686376,memoryutilization:
> > > 50%.
> > > Has anyone been able to solve this problem onSQLServerStd Edition ?
> > > I know the OS is trimming theMemorybut apparently I have been
> > > unable to find a way for this to stop.
> > > "lock pages inmemory" is disregarded in Std Edition.
> > > Any thoughts ?
> The Box has 12GB of RAM.
> SQL Server max memory is set to 8GB.
> Windows is patched to SP2.
> I am copying though "very large" backup files (around 70~100GB ) from
> and to the box.
> Is there *anything* I can do?
I have to correct the data:
The Box has 16GB of RAM.
SQL Server max memory is 10GB
The rest is the same.|||1) You did not answer my question about other services/apps running on this
box.
2) What version and is it 32/64 bit of sql server are you running?
3) Consider setting minimum sql server memor to see if this prevents the
paging. Also, have you been able to tie the paging to a specific event on
the server?
--
TheSQLGuru
President
Indicium Resources, Inc.
<isyourfriend@.gmail.com> wrote in message
news:1183642164.966037.25340@.q75g2000hsh.googlegroups.com...
> On Jul 5, 9:19 am, isyourfri...@.gmail.com wrote:
>> On Jul 2, 11:57 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
>>
>> > Are other processes running on theserver? This is suboptimal.
>> > How much RAM total? If < max allowed, add ram.
>> > Make sure your drivers and OS andsqlserverare fully patched. There are
>> > numerous known bugs in the wild that will flush ram.
>> > --
>> > TheSQLGuru
>> > President
>> > Indicium Resources, Inc.
>> > <isyourfri...@.gmail.com> wrote in message
>> >news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
>> > >Asignificantpartofsqlserverprocessmemoryhas been paged out.
>> > > This may result in a performance degradation. Duration: 0 seconds.
>> > > Working set (KB): 349620, committed (KB): 686376,memoryutilization:
>> > > 50%.
>> > > Has anyone been able to solve this problem onSQLServerStd Edition ?
>> > > I know the OS is trimming theMemorybut apparently I have been
>> > > unable to find a way for this to stop.
>> > > "lock pages inmemory" is disregarded in Std Edition.
>> > > Any thoughts ?
>> The Box has 12GB of RAM.
>> SQL Server max memory is set to 8GB.
>> Windows is patched to SP2.
>> I am copying though "very large" backup files (around 70~100GB ) from
>> and to the box.
>> Is there *anything* I can do?
> I have to correct the data:
> The Box has 16GB of RAM.
> SQL Server max memory is 10GB
> The rest is the same.
>|||On Jul 5, 11:15 am, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> 1) You did not answer my question about other services/apps running on this
> box.
> 2) What version and is it 32/64 bit of sql server are you running?
> 3) Consider setting minimum sql server memor to see if this prevents the
> paging. Also, have you been able to tie the paging to a specific event on
> the server?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <isyourfri...@.gmail.com> wrote in message
> news:1183642164.966037.25340@.q75g2000hsh.googlegroups.com...
> > On Jul 5, 9:19 am, isyourfri...@.gmail.com wrote:
> >> On Jul 2, 11:57 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> >> > Are other processes running on theserver? This is suboptimal.
> >> > How much RAM total? If < max allowed, add ram.
> >> > Make sure your drivers and OS andsqlserverare fully patched. There are
> >> > numerous known bugs in the wild that will flush ram.
> >> > --
> >> > TheSQLGuru
> >> > President
> >> > Indicium Resources, Inc.
> >> > <isyourfri...@.gmail.com> wrote in message
> >> >news:1183390681.575465.86070@.57g2000hsv.googlegroups.com...
> >> > >Asignificantpartofsqlserverprocessmemoryhas been paged out.
> >> > > This may result in a performance degradation. Duration: 0 seconds.
> >> > > Working set (KB): 349620, committed (KB): 686376,memoryutilization:
> >> > > 50%.
> >> > > Has anyone been able to solve this problem onSQLServerStd Edition ?
> >> > > I know the OS is trimming theMemorybut apparently I have been
> >> > > unable to find a way for this to stop.
> >> > > "lock pages inmemory" is disregarded in Std Edition.
> >> > > Any thoughts ?
> >> The Box has 12GB of RAM.
> >> SQL Server max memory is set to 8GB.
> >> Windows is patched to SP2.
> >> I am copying though "very large" backup files (around 70~100GB ) from
> >> and to the box.
> >> Is there *anything* I can do?
> > I have to correct the data:
> > The Box has 16GB of RAM.
> > SQL Server max memory is 10GB
> > The rest is the same.
1) there are other scripts copying *very large* backup files around.
2) this is x64 SQL Server 2005 Standard Edition built 3161
3) It *does* happens when copying those large files
Now, is there a way to prevent this Huge Memory Flush ?
-Noel