Limiting Exchange 2010 SP1 Database Cache

Some time ago, I blogged about on how to limit the amount of memory Exchange 2010 can allocate for database cache. After the introduction of Exchange 2010 Service Pack 1 this didn’t seem to work anymore, as many people reported.

After some investigation, it turns out you also need to set the msExchESEparamCacheSizeMin value for Exchange 2010 SP1?s cache manager to honor the minimum and maximum limits for allocating database cache memory.

To show you this, I’ll first show Exchange 2010 SP1 where I only set msExchESEparamCacheSizeMax. In this example, I’ll use a value of 1024 which corresponds to 32 MB (1024 * 32kb pages). I then turned on Performance Monitor and started monitoring the following MSExchange Database Cache\Information Storecounters:

  • Database Cache Size, the current allocated database cache size;
  • Database Cache Size Min, the minimum database cache size;
  • Database Cache Size Max, the maximum database cache size.

Continue reading

Written by

Matthew Glover
Have a question or problem?
I can't guarantee an answer, but I'll try. Drop me a message!


Follow glovario on Twitter

Windows Service Pack 3 [SP3]

Windows XP is maturing. First came Service Pack 1 (SP1), then SP2 and now a few years later it’s time for SP3. Since Vista hit the shelves almost a year ago, XP has been rolling along in the background, quietly taking care of business on the majority of desktops in use today. With the release of Service Pack 3 (SP3) just around the corner in the first part of 2008 it will undoubtedly draw some renewed attention to XP. In advance of the final version of SP3, Microsoft has made available Release Candidate 1 (RC1) of XP Service Pack 3 (SP3). A Release Candidate is not intended for production or mission critical systems, but for testing purposes it is fine. As always, make sure you have full tested backups of all your systems and data before you do any experimenting.
Continue reading