Windows Server

Adam Butler · Guest

Hi,

Been running SBS 2003 for a year and a half now.
All of a sudden my memory usage by sqlservr.exe has shot from 70 to over 500
Mb.

I have always had three instances of sqlservr running and at most I'd see
maybe 70 Mb on the highest one. Now, I see over 500 Mb for the high one and
the other two are still normal at 38 and 19 Mb or so each.

I read some old posts and they had a command to limit the memory usage but I
get an error and I assume it is from the fact that I'm running Standard
edition.

Can I do anything to reduce the memory usage?
I did reboot the server and it has helped but the usage is slowly creeping
back up over 100 Mb after only 24 hours.

David Copeland [MSFT] · Guest

Adam,

Can you run the following command from a command prompt to find out the
process id's to the different instances..

tasklist /svc

Then open up Task Manager, click on the Processes tab (note that you may
need to click on the View/Select Columns option to make sure that the PID
(process identifier) option is selected), the look for the different process
id's to see which process id is using the memory.

--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

Adam Butler · Guest

Yep,
Did your commands and:
MSSQL$SBSMONITORING

This seems to be the one eating memory.

David Copeland [MSFT] · Guest

Adam,

Are you using the following? If so, what error do you get?

osql -E -S servername\sbsmonitoring

Adam Butler · Guest

Hi David,
The commands seemed to work.

Thanks Much for the help!

Adam

MarkJ · Joined: 18 Oct 2007 Posts: 1

Heey,

I know this is an old thread but i have the same problem. My sqlsrv eats up a total of 1.2GB! mem..

I followed david steps but when i looked at the task list matching my PID in command prompt my PID is NOT MSSQL$SBSMONITORING but it is MSSQL$MSFW.

The sqlsrv MSSQL$SBSMONITORING is fine running at a mem usage of 77mb..

My question is can i go on with david's following steps or do i need to take other actions... if so which?

Thanks

MarkJ

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1