Transaction logging has been around a long time — since release 5 of IBM® Lotus® Domino® — and it has proven its business worth in deployments across a wide spectrum of enterprises and applications. But for some who first tried transaction logging in earlier releases, there are lingering doubts and worries stemming from problems they may have encountered, which often were the result of not knowing the best practices to use with this feature. Today, there´s good reason for every Domino customer to understand and use transaction logging. The numerous improvements to transaction logging in newer releases provide compelling business value. And for any administrator who plans to use the Domino Attachment Object Service (DAOS) in 8.5, coming to terms with transaction logging is a must, as DAOS requires it.

We´ll put you on solid ground with transaction logging — explaining the fundamental concepts and logging options, highlighting the business value and use cases, and giving you an accurate picture of the feature as it exists today. We´ll address the fear, uncertainty and doubt (FUD) surrounding transaction logging, and the myths that have circulated among the Domino customer community concerning this feature. As we explode the myths, we´ll go a step farther by explaining how to address the underlying concerns and resolve issues via best practices. In short, we´ll help you to achieve the optimal value of Domino transaction logging.