At times, depending on the isolation level or table hints (which the reporting engine sometimes provides), multiple locks will be opened for a single query. Post-processing to roll these multiple lock events up for auditing purposes may become arduous so I am considering standing up a front-end database that will contain one VIEW per table in the snapshot to act as a pass-through. For example if there is a table in the snapshot named dbo.Product there will be a VIEW in the front-end database named dbo.Product that will contain the query SELECT * FROM SnapshotName.dbo.Product. I can then add a Database Audit Specification to the front-end database since it is not read-only. Keeping users away from directly querying the Snapshot (and losing the audit trail) should not be an issue because of the way the rest of the reporting area is setup.