Link to home
Start Free TrialLog in
Avatar of david_32
david_32

asked on

dbcc take ups all may buffer cache

Hi when I run a dbcc it seems to take up all my buffer cache. That is to say after dbcc my ring buffers report a %100 Utilization, target and total memory are the same (before hand the total is lower). How can I stop the dbcc using all the buffer cache?
Avatar of Mark Wills
Mark Wills
Flag of Australia image

What dbcc commands are you running and how frequently ? Some of them can use a lot of resource, some require exclusive access...
Kindly provide me the command which you exactly used.
@rrjegan : it should be "us", not just "me", we are all trying to help :)
If you check the time gap between our posts, you may get why I meant me over there..
When I started typing, there was no posts, that's why..

We are Experts and we have something in common...
Cheers..
@rrjegan17: Didn't notice - sorry about that - yeah, my lack of refreshes covers hours, at least yours was a minute - seconds maybe... BTW, how are you enjoying EE - see that you are still tracking very well...
Superb..
Enjoying it..
And by helping others I feel I am replenishing my knowledge gathered till now..
By the way, just one and half months old in EE, I am not aware whether any private chats between experts is available or not.. Can you guide me on that if you are aware...

david_32,
    Kindly tolerate for asking these things in your question..
Avatar of david_32
david_32

ASKER

dbcc checkdb('databasename')  Is what I am running. The <instance>.memorymanager.total_memory  is much less than <instance>.memorymanager.target_mem before I run and after running they are equal which would indicate to me a stress in buffer cache. It does not seem to relieve itself afterwards.
david_32

Not neccessarily. Target memory is the computed amount of memory that SQL would like to be able to use. think of "target" as being the ideal goal.
It simply means of the target memory, the amount currently in use is less than it could be before you begin...

More accurately, Target is the number of 8-KB pages it can commit without causing paging. Need to check other metrics such as Private Bytes, or Buffers to work out if there are real memory pressures, and dbcc checkdb is not a good gauge - it should not be run all that often, and not during active time unless you have good reason to do so. Memory does not automatically release - it does get reused, and as time goes by with no additional memory pressures, those tasks do eventually release memory.
rrjegan17

yeah they are trialing a exports chat in the beta edition at the moment. In the meantime, my e-mail is on my bio, and you can certainly use it - can point out or maybe answer a few questions for you.

Hi Mark,

yes.. I think understand that - but isn't total memory the amount of memory the instance is actually using. If this increases to the same amoount as the target and stays there.. don't you have paging and hence memory stress?
ASKER CERTIFIED SOLUTION
Avatar of Mark Wills
Mark Wills
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks .. it didn't directly answer my question but has heaps of helpful info!