Link to home
Start Free TrialLog in
Avatar of bruce_77
bruce_77

asked on

Exchange 'checkpoint depth'

Hi

I have been searching for a simple explanation of checkpoint depth in relation to Exchange transaction logs, but I can't seem to find one. Could someone please explain to me or point me in the direction of a recommended link?

...and is a large checkpoint depth good or bad? I just can't get my head around it!
Avatar of coolsport00
coolsport00
Flag of United States of America image

See: http://msexchangeteam.com/archive/2006/09/08/428860.aspx

Let me know if this is what you're wanting.

Regards.
~coolsport00
Checkpoint Depth is....

"The maximum amount of data that the Extensible Storage Engine can write to logs before it writes to the database."

Or in simple language "the number of transaction logs which are not committed to database."

This is 20MB for Exchange 2003 normally.

Large checkpoint depth is not good, specially when backup is going on store.exe doesn't write the data into database and logs getting increases. If huge amount of mail flow happen or you do the mailboxes move and Exchange has a behavior to dismount the database if checkpoint depth reaches to some amount (exchange 2003 = 1008 & Exchange 2007 = 5000, this doesn't apply for Exchange 2007 SP1) then it dismount all the databases in the Storage Group.
http://theessentialexchange.com/blogs/michael/archive/2008/04/28/ESE-Checkpoint-Depth.aspx
Avatar of bruce_77
bruce_77

ASKER

Hi Amit,

Ok, thanks..

So, if the Checkpoint depth for Exchange 2003 is 20MB, then does this mean that the maximum amount of logs that ESE can write to before commiting to the database is 4 (i.e. 5MB x 4)?

After this point, ESE will write to the database regardless?

So, its good to keep the checkpoint depth fairly small?
ASKER CERTIFIED SOLUTION
Avatar of AmitTank
AmitTank
Flag of United States of America 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