When Transaction logs get committed in Database of Exchange 2007 / 2003

Whenever Exchange has the time for it but probably not that long If Exchange is very busy this can take longer It depends on your configuration, I don't think there are any good number on it You can verify this: http://exchangeis.com/blogs/exchangeis/archive/2007/05/28/using-eseutil-how-to-check-which-transaction-log-files-are-not-committed.aspx Deli

Hi, Transaction Logs are committed to DB, when (some of the ways off course, not all): Exchange Information Store service is stopped cleanly, in a proper way, which is the normal stop service process. when you do a full backup or copy backup i think. also, there is something called CheckPoint Depth, where by it specify how much the ESE engine can write to before commiting to the DB. The checkpoint depth is basically the size (in megabytes) of log files to keep in memory. Any database page referred to by those log files can be delayed in writing to the database. The default checkpoint depth for Exchange 2000/2003 is 20MB per SG. This 20MB is the size of the logs, not the size of the pages referred to by the logs. check the following links to read about the CheckPoint Depth: http://blogs.technet.com/dbordini/archive/2006/09/09/455003.aspx Hint: Check the English part not the other lanugage at the begining of this blog please let me know if the above information and link were helpful to you. Regards,