November 11, 2011 at 12:14 pm
SQL_DBA_New (11/11/2011)
Hi,The IT team came running to us..
Later on... we were keeping an eye on it.
We did a reboot on Thursday then on Monday..
There were no multiple logins i=on Monday. 1 job was running ... and it was of for Data warehouse work.
It has lot of cursors..
Tell the IT team that SQL Server often will take up as much memory as the server will let it. It's not a problem, and not something they need to worry about.
Open up Activity Monitor (right-click the server in the Object Explorer in Management Studio and pick Activity Monitor), and go to Resource Waits. You want to look at the row for Memory, and see if it is unusually high. If so, you need to track down what's causing the resource waits. The "Recent Expensive Queries" part of Activity Monitor can help you find that.
Most likely, though, SQL Server is just taking memory because it needs it for a job or query or whatever, and this is a non-situation.
If you want a fast way to find out what's going on and what's eating up resources, etc., in SQL Server, I recommend downloading a copy of Confio Ignite and using that. Very helpful in that task.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply