Reign In SQL Memory hogging
-
Rebooting my dev machine is a chore now; i've only got 3 databases, and they are about 2 gig total...not all that big; but after any reboot, or stop and start of my SQL instance, it takes literally 10-12 minutes of SQL server thrashing my harddrive, jumping to use 1.8 gig plus of my 2 gig ram, before it finally settls down to use 1.5 gig of ram.
only myself and the other occasional dev guy connect to my machine.
I thought by changing settings show below, I could limit SQL to a certain amount of RAM, but it doesn't seem to care what values I've placed there, it will always sspike over 1.5 gig;
after that 10-12 minute window, i can start other programs, like Visual Studio, and SQL Server will reluctantly give up some RAM for other applications. Inside that 10-12 minute window, I'm dead in the water and might as well go to the quickie mart or something while I'm waiting.
thinking the problem was me, i detatched EVERY SINGLE database, leaving just system databases.
then i stopped and started the service again.....same thing...slamming the harddrive and jumping to 1.5 gig of ram no matter what.
also, there are no jobs, service borkers or anything on this machine...it's just a dev platform.
can anyone tell me what I'm missing?
Lowell
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible! -
The first thing I noticed is that you have min memory set to 200000MB .... a bit larger than you would like! That shouldn't have any bearing on your problem as SQL won't allocate the minimum until it's required; you should drop it to something more appropriate though (like 200).
The only possibilities that I can think of at present are massive fragmentation on your drive (although you would need to have huge system databases for any significant effect) or antivirus/some other process causing contention.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply