Re: 'A significant part of sql server process memory has been paged ou

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I spoke with the correct people at Microsoft about this at the PASS Summit a few weeks ago. This is not expected behavior for Standard Edition but is a common experience in the field. The discussion also had some people from the SQLCAT group that confirmed thae observerd behavior was consistent with their experiences when Enterprise Edition did not have the "lock pages' right. Microsoft is re-examining the "lock pages in memory" as an Enterprise-only feature. No guarantees they will move the feature to Standard Edition, but they are now treating it as a stability issue rather than an scalability issue. As long as it was a scalability issue, there was zero chance of a fix. As a stability problem, we might get some relief. Now we wait and see.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Igor Marchenko" <IgorMarchenko@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D0FF0FF0-7D8A-4520-8122-1709377C0F57@xxxxxxxxxxxxxxxx
Hello!

This is a follow up to my previous post:
'
We have just configured SQL Server 2005 64-bit two node active/passive
cluster with 32 GB of RAM. I have limited SQL Server memory usage to 26 GB.
Total Server Memory (KB) shows value 16MB at the moment. Target Server Memory
(KB) is showing 27262976 (26 GB).
...'.
I have noticed that there are multiple messages (not just on start up) in
SQL Server error log:

'Message
A significant part of sql server process memory has been paged out. This may
result in a performance degradation. Duration: 331 seconds. Working set (KB):
95276, committed (KB): 204776, memory utilization: 46%.
'.

We are running SQL Server 2005 SP2 64-bit Standard Edition on Windows 2003
Enterprise R2 64-bit and 'Lock Pages in Memory' is ignored.
I did some research and the general consensus is if this error only shows
up on start up it is OK. But it is not the case in my enviroment. I am really
concerned about performance implications and hesitant to start using this
enviroment.
Any advice is greately appreciated.

Thanks,
Igor

.

Relevant Pages

  • Re: Microsoft Forefront Client Security on SBS 2003 R2
    ... purchase the SQL 2005 standard edition as well as the CALs just as Cris ... we can install SQL Server 2005 Standard Edition on Windows Small ... SQL Newsgroup: microsoft.public.sqlserver.server ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Install Sql Server on Win 2003 Small Business?
    ... The premium edition includes everything in the standard edition, ... Microsoft SQL Server 2000, ... I suspect that you have standard edition and it restricts you from adding ...
    (microsoft.public.sqlserver.server)
  • Re: MS SQL and Web edition 2003
    ... >> MSDE will run on W2003 web edition, the full version of SQL Server ... Microsoft SQL Server™. ... I have MS>>> SQL server 200 Standard edition, but it does not seem to work. ...
    (microsoft.public.windows.server.general)
  • Re: Cant create a publication in SQL Server 2005
    ... Have a look under Computer Management (Services and Applications, Microsoft ... SQL Servers) - maybe you have really installed the Standard Edition as well ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)
  • Critical Alert Update - W32.Slammer
    ... It's not clear if SQL Server 2000 SP1/SP2 includes the ... Microsoft SQL Desktop ... and all applications that install ... >most recent cumulative SQL Server security patch, ...
    (microsoft.public.security)