When reporting on audit data, you should be sure that only committed data is included in the report. Due to the way ABL and SQL clients and the database work, it is possible that the database might contain interim audit data that could be rolled back in the event of a failed transaction. Therefore, if you are reporting against an operational database that has auditing enabled and active, it is important that the audit data be read SHARE-LOCK to avoid reads on uncommitted data resulting in inaccurate audit reports.