we always install the HP management software, anti-virus, Emulex HBA Anywhere. The HP software also installs a light version of Apache or Tomcat, forget which one. a lot of people will also install SSIS and other SQL components other than the database engine as well as other database vendors' drivers

Jeff Moden (10/16/2009)Heh... wouldn't a reasonable alternative be to only have SQL Server on the SQL Server box?

Unfortunately not. I've heard of a case where SQL was the only thing installed on the box (other than OS) and and it was still getting paged out if max memory was set about about 60% of the total memory. This is a server with >16GB.

few years ago Emulex and Windows 2003 x64 SP2 had an I/O bug and it caused one of our servers to lock up and reboot. MS released a series of hotfixes and everyone from Emulex to HP released updated drivers for HBA's and RAID controllers

Jeff Moden (10/16/2009)Heh... wouldn't a reasonable alternative be to only have SQL Server on the SQL Server box?

On the face of it, yes. And, most of the time, this will work well. However, you are then at the mercy of Window's memory manager - any sudden requests for memory from any other process are likely to result in some of SQL Server's address space being paged out. It is an inviolable law of the universe that it will occur at the most inconvenient time.

There are many things that can cause sudden demands for memory from Windows, even if you lock the server down and carefully control who has access and what processes can run. Not being able to lock memory for SQL Server on 64-bit Standard Edition just introduced a whole new set of avoidable problems.

Yeah, but what I was wondering was if it was really needed. Back a few years ago I read someplace it wasn't necessary to set it up but I'm doing it anyhow. Just recently experiencing I/O messages. Thanks.

Kristy Lanter (10/27/2009)Yeah, but what I was wondering was if it was really needed. Back a few years ago I read someplace it wasn't necessary to set it up but I'm doing it anyhow. Just recently experiencing I/O messages. Thanks.

Personally, I always enable it. You don't say what the I/O messages say...?This article was about lock pages in memory on Standard Edition and the message that can appear to say that a significant part of SQL Server's allocated memory has been paged out. Is that what you're seeing?

Just researching issues we have that really are not related to the article but came across this article and got me thinking. I was able to lock the issue down to a peice of code that when submitted locked the floor down (casino) and disabled it. Things are good now, just need to fix that code. Good article though.

Is this update required for an environment running SQL Server 2008 SP1 Standard 32-bit using AWE and PAE in order for Lock Pages in Memory to be functional? I only see 64-bit referenced in the various posts that I've seen. Thanks.