Can't run MMC without pagefile?

[Guest Neufusion]

I followed the procedures at http://support.microsoft.com/kb/889654/

to determine the appropriate page file size for a Windows Server 2003

x64 server running SQL Server 2005 x64 with 16gb of RAM.

 

The article stated "When lots of memory is added to a computer, a

paging file may not be required.". and "If you have enough RAM

installed in your computer, you may not require a page file at all,

unless one is required by a specific application."

 

I monitoring the paging file and determined it had little to no usage.

So I decided to test out the scenario of running with 'no paging file'

on a SQL Server 2005 x64 mirror server. I set the virtual memory

settings to 'No Paging File' and restarted the server. It came up and

ran through night and through a heavy batch update of the database. In

the morning, I logged in to check on the status of the server.

Everything in SQL worked fine. When i logged in, I could not open

Performance tool or any other tool that runs inside MMC. It would give

an error of "Paging file is too small". I checked my performance logs

and there was always at least 520mb of available memory the entire

time.

 

Are MMC and Computer Properties some of the "specific applications"

that require a pagefile?

 

If so, why is MS suggesting that you may not need one? MMC and

Computer Properties seem like pretty mission crtical applications to

me...

[Guest Mathieu CHATEAU]

Re: Can't run MMC without pagefile?

 

Hello,

 

can you access things from remote, like eventlog ?

Do you have MMC 3.0 ?

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"Neufusion" <mikeymiller@gmail.com> wrote in message

news:1192736339.729216.229710@v23g2000prn.googlegroups.com...

>I followed the procedures at http://support.microsoft.com/kb/889654/

> to determine the appropriate page file size for a Windows Server 2003

> x64 server running SQL Server 2005 x64 with 16gb of RAM.

>

> The article stated "When lots of memory is added to a computer, a

> paging file may not be required.". and "If you have enough RAM

> installed in your computer, you may not require a page file at all,

> unless one is required by a specific application."

>

> I monitoring the paging file and determined it had little to no usage.

> So I decided to test out the scenario of running with 'no paging file'

> on a SQL Server 2005 x64 mirror server. I set the virtual memory

> settings to 'No Paging File' and restarted the server. It came up and

> ran through night and through a heavy batch update of the database. In

> the morning, I logged in to check on the status of the server.

> Everything in SQL worked fine. When i logged in, I could not open

> Performance tool or any other tool that runs inside MMC. It would give

> an error of "Paging file is too small". I checked my performance logs

> and there was always at least 520mb of available memory the entire

> time.

>

> Are MMC and Computer Properties some of the "specific applications"

> that require a pagefile?

>

> If so, why is MS suggesting that you may not need one? MMC and

> Computer Properties seem like pretty mission crtical applications to

> me...

>

[Guest Neufusion]

Re: Can't run MMC without pagefile?

 

I restarted the server and put a 512mb page file on. The server ran

fine... MMC worked with everything.

 

So just now I set it back to "no paging file" and restarted... The

sever comes up and has 14gb of 16gb free ram. The SQL instance is only

using about 250mb at the moment. Computer Properties and using some

MMC apps work. But when I try to load the .NET 2.0 Framework on it, it

bombs out with a mmc.exe error on kernel32.dll.

 

I'm just going to set it back to 512mb and monitor it closely for a

couple days. For the time it was running at 512mb, there was only 0.8%

max page file usage, so it could potentially be lowered a lot more.

 

I just dont understand why not having the page file is affecting

system applications...

 

On Oct 18, 2:36 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:

> Hello,

>

> can you access things from remote, like eventlog ?

> Do you have MMC 3.0 ?

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog:http://lordoftheping.blogspot.com

> French blog:http://www.lotp.fr

>

> "Neufusion" <mikeymil...@gmail.com> wrote in message

>

> news:1192736339.729216.229710@v23g2000prn.googlegroups.com...

>

>

>

> >I followed the procedures athttp://support.microsoft.com/kb/889654/

> > to determine the appropriate page file size for a Windows Server 2003

> > x64 server running SQL Server 2005 x64 with 16gb of RAM.

>

> > The article stated "When lots of memory is added to a computer, a

> > paging file may not be required.". and "If you have enough RAM

> > installed in your computer, you may not require a page file at all,

> > unless one is required by a specific application."

>

> > I monitoring the paging file and determined it had little to no usage.

> > So I decided to test out the scenario of running with 'no paging file'

> > on a SQL Server 2005 x64 mirror server. I set the virtual memory

> > settings to 'No Paging File' and restarted the server. It came up and

> > ran through night and through a heavy batch update of the database. In

> > the morning, I logged in to check on the status of the server.

> > Everything in SQL worked fine. When i logged in, I could not open

> > Performance tool or any other tool that runs inside MMC. It would give

> > an error of "Paging file is too small". I checked my performance logs

> > and there was always at least 520mb of available memory the entire

> > time.

>

> > Are MMC and Computer Properties some of the "specific applications"

> > that require a pagefile?

>

> > If so, why is MS suggesting that you may not need one? MMC and

> > Computer Properties seem like pretty mission crtical applications to

> > me...- Hide quoted text -

>

> - Show quoted text -