SQL 2005 x64 memory usage (and leakage)

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
mchad65Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
go to the sql server parameters, and set the MAX MEMORY setting to 3500 (MB)
0
mchad65Author Commented:
Ok, did that.  So I assume that will prevent SQL from crashing the server?
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
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
mchad65Author Commented:
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
Guy Hengel [angelIII / a3]Billing EngineerCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.