Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Setup / December 2005

Tip: Looking for answers? Try searching our database.

sqlservr process sucking memory

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David Lozzi - 29 Dec 2005 16:15 GMT
Howdy,

I have MSDE 2000 running on my WinXP Pro SP2 workstation and its only
running one database for my local intranet. I am the only one accessing the
page and at most it loads about 60 links, very lightweight app. The process
sqlservr is at 113MB of mem usage and 123MB of virtual memory. Why? If I
stop SQL and restart it it drops to about 20MB but then climbs back up and
keeps going! What is causing it to get so large? Again, its such a small
lightweight database.
My development server, MSSQL2000 on Win2k3 Standard, has more databases and
is hit by more users. There are two instances of sqlservr totaling 120MB.
One of my customer's production machines, MSSQL2000 on Win2k3 SBS Premium,
has 4 instances of sqlservr totaling 300MB mem and 340MB virtual.

Now with all that said, is there anything that can be done to reduce the mem
usage on my workstation, development box and even the production box? The
production box isnt too bad, but my workstation could use a break. I usually
operate around 1.6GB memory and 2.5GB virtual. I'm just trying to reduce
some items to gain performance.

Thanks for your time!

Signature

David Lozzi
Web Applications Developer
dlozzi@(remove-this)delphi-ts.com

Andrew J. Kelly - 29 Dec 2005 17:50 GMT
How large is the database that you have on that instance?  SQL Server will
use as much memory as you have available if it thinks it can use it. But my
guess is that your procedure cache is very big and that is what is taking up
most of the memory.  If you run adhoc queries instead of stored procedures
or parameterized queries that can be reused you can suck up a lot of memory
with the procedure cache.  One thing you can try to reduce the overall
amount that SQL server uses is setting the MAX Memory setting.

Signature

Andrew J. Kelly  SQL MVP

> Howdy,
>
[quoted text clipped - 18 lines]
>
> Thanks for your time!
David Lozzi - 31 Dec 2005 15:42 GMT
I am using stored procs for everything. The MSDE database is two tables, 60
records total.

Signature

David Lozzi
Web Applications Developer
dlozzi@(remove-this)delphi-ts.com

> How large is the database that you have on that instance?  SQL Server will
> use as much memory as you have available if it thinks it can use it. But
[quoted text clipped - 27 lines]
>>
>> Thanks for your time!
Andrew J. Kelly - 31 Dec 2005 15:48 GMT
Are you calling the stored procs as an RPC call or a Batch?  Two tables with
only 60 rows should not utilize any where near that much memory.  Can you
post the output of DBCC MEMORYSTATUS?

Signature

Andrew J. Kelly  SQL MVP

>I am using stored procs for everything. The MSDE database is two tables, 60
>records total.
[quoted text clipped - 31 lines]
>>>
>>> Thanks for your time!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.