March 27, 2014 at 1:13 am
GilaMonster (3/27/2014)
tony28 (3/26/2014)
Guys, I understand that you dont understand why I want to do, but it looks that we have problem with disk subsystem.It is not possible to buy new or upgrade.
I was thinking about clean memory with statement such as if I will restart service or testing AlwaysOn function. We have 170GB memory and for SQL is 140GB and one week with rebuild index and update statistics, it can handle without problem. For example I found one query on our website for users that memory increased about 10GB after one query was executed. If it is possible I fix it. I have to find if is it possible to prevent increasing memory during these operations and I think that it will be very helpful.
I think that I can change to Simple recovery mode. This is just for less disk space of log file or it concern also memory ? Or next advice?
And Do you know this script above?
March 27, 2014 at 2:24 am
tony28 (3/27/2014)
I was thinking about clean memory with statement such as if I will restart service or testing AlwaysOn function.
What for? SQL is capable of managing its own memory, you don't need to do things like fail over a cluster or restart the service.
If SQL is using too much memory, reduce max server memory. Otherwise you generally leave it alone and let it manage its own memory.
I think that I can change to Simple recovery mode. This is just for less disk space of log file or it concern also memory ? Or next advice?
Neither. Simple recovery is for when you don't need to be able to recover to a point in time, when it's acceptable to lose all data back to the last full backup in the case of a disaster.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply