current community

your communities

more stack exchange communities

Stack Exchange
tour help
stack overflow careers
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 0 down vote favorite

I have an ASP.NET MVC app that I am developing, very few users but SQL Server is hogging memory like crazy.

I am wondering if it could be due to the Entity Framework. I have been following tutorials and books like ASP MVC Pro 2 for guidance but none of them show to explicitly dispose of the data context.

If you don't dispose of it, does SQL Server continue to hold memory for the request?

Any help or suggestions would be greatly appreciated,

share|improve this question

1 Answer 1

up vote 1 down vote accepted

You should of course dispose ObjectContext / DbContext. That is why it implements IDisposable. But your problem is not related to not disposing ObjectContext because SQL server hanldes its memory without any relation to client. You should check how many data are processed in your queries.

share|improve this answer
    
the problem is that there are no queries running but yet the server is using over 3GB of memory –  AnonUser Mar 10 '11 at 16:01

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.