Michael asks: > ...if your application is not coded for logical transactions, >would you still recommend the use of logging, or would >you recommend a hardware alternative (high availability >arrays, mirroring, etc.)? I would recommend logging, especially if cost is an issue. For minimal cost, a good backup strategy and image logging roll-forward recovery offers very good data protection. I also agree with Elbert's other reason's for logging. > Audit trails (using an appropriate log list program) > To review how a program works > To help debug a new program > To see who changed something really recently > To analyze performance issues > .. more .. Especially the audit trail. Our auditors love it. So that even in a shop where high availablity options have been implemented there are still reasons to use image logging. Our shop uses netbase shadowing, user volume sets, and image logging in conjunction with a very aggressive online backup strategy. -- ************************************* ** ** ** Chad Gilles ** ** Sr. Software Analyst ** ** ------------------------------- ** ** American United Life ** ** One American Sq. ** ** Indianapolis, IN 46206-0368 ** ** ------------------------------- ** ** Ph. 317-263-1423 ** ** Fx. 317-263-1956 ** ** EM. [log in to unmask] ** ** ** *************************************