Solved

SQL 2005 x64 memory usage (and leakage)

Posted on 2008-10-10
5
240 Views
Last Modified: 2012-05-05
I just set up a new SQL2005 server standard edition x64 on win 2003 server x64.  The box is a quar core xeon with 4 gigs of ram and a 6 gig swapfile on a partition other then the sql install or the db partitions.  Our developers moved applications from a SQL2000 (Standard, x32) server on to the 05 box.  What has been happening is that over the course of the day, page file useage rises.  It gets up to about 3.9gigs, even though the CPU's activity is nill (1-2% or so).  Once it gets that high, I start panicing and restart the SQL service (late at night, as not to drop active sessions) and it drops to about one gig.  Then it begins it's rise again.  

Now, the server hasn't crashed, or become unresponsive yet, but historically, when our SQL2000 boxes started a rise like this, it ended badly...  

So my initial assessment was a memory leak in one of the applications using the server, but none of the developers can identify any problem with their code (all asp.net web apps).  So my thoughts went to x64 SQL 2005, that maybe this is a normal condition?

Any comments?

Thanks
0
Comment
Question by:mchad65
  • 3
  • 2
5 Comments
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 22686425
go to the sql server parameters, and set the MAX MEMORY setting to 3500 (MB)
0
 

Author Comment

by:mchad65
ID: 22686791
Ok, did that.  So I assume that will prevent SQL from crashing the server?
0
 
LVL 142

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 22686821
it will make that SQL Server will stop taking memory for it's usage at 3.5GB, avoiding that sql server and any other apps on the server start swapping, and resulting in all the apps slowing down to a crawl ...
0
 

Author Comment

by:mchad65
ID: 22686845
As I suspected.  The box is dedicated to SQL only.  

Regarding my original question, looking at the memory utilization I described, would you call that a memory leak, or normal sql 2005 operation?
0
 
LVL 142

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 500 total points
ID: 22686961
it's normal operation. sql server will try to put all the data, as tables are queried, into memory.
means also that if all the db tables together only have 1GB, sql server will not use much more than 1GB of RAM neither.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

INTRODUCTION: While tying your database objects into builds and your enterprise source control system takes a third-party product (like Visual Studio Database Edition or Red-Gate's SQL Source Control), you can achieve some protection using a sing…
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now