Windows Forum

Ask something
Discussion Locked

SQLServr.exe eating too much memory

0 helpful
7 replies

by faisalmasood 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a 3 tier ASP based application running IIS 5 in the Frontend & SQL 2000 in the backend. COM+ is running in middle tier. Clients are using this application over the internet.

The OS is Win2000 SP3 with SQL 2000 SP3 with all latest updates.

The problem we are facing for few days is that SQL server process (SQLSerVr.exe) is taking too much memory. Once SQL memory consumption start rising, it doesn't come back to normal untill we restart the server.

The server has got 1 gig of memory. We have checked the SQL in detail but nothing suspicious has been found. We've even deployed the DB on another server but still the same issue on the new server as well.

We have scanned the servers for viruses well & nothing found. There are few errors in EventViewer, but nothing related to SQL server.

Now we need to know:

1) Any idea what is cauing SQL to behave in this way?

2) Is there a way we can check what processes, threads & handles are runnning inside SQLSrvVe.exe process?

3) How to detect identify this SQL problem?

Your comments & suggestions are are highly appreciated.

7 replies

by cactus pete

On of the settings in SQL will allow you to set the maximum level of RAM used by the program. I can't think of it on the top of my head, but I'll take a look for it on one of my servers. SQL will take all the RAM you let it, and it never gives it back. That's why this setting exists.

by cactus pete

Right click on the server [in enterprise manager] and select properties. On the memoery tab, use the slide rules to limit the mount of RAM SQL can access.

by hpw3

1. If you have "Use a fixed amount of memory" in the Memory configuration settings dpetrak is right > SQL will take up that memory and keep it. If you change the setttings to "Dynamically configure SQL memory" it should release memory when not in use. (right click server in Ent Manager > Properties > Memory Tab)

2. As for what processes are in use you can get a general idea from going to Ent Manager > Management > Current Activity > Process info

3. Verify the configuration settings. Record current memory usage, stop and re-start SQL and check to see if memory useage is the same. If so, you probably have "Use a fixed amount of memory" set as the default.

This discussion is closed to new replies.