As part of a comprehensive security policy, a company can require the ability to retroactively go back a set number of years and analyze the effects of any particular request against certain tables in their database.
A company must institute a policy of archiving their weekly backups and associated log files such that they can reconstitute the database for any chosen moment in time.
To allow, at any future time, the replay and analysis of any request against the relevant, restored database, sufficient database audit information must be captured about every request made against the database. This requirement can cover both static and dynamic SQL statements. The EXECUTE category, when logged WITH DATA contains the necessary information to replay past SQL statements, assuming that the data in the database is restored to the state it was when the statement was issued.
Restrictions
To enable replay of past activities, as the SECADM:
Your environment is now set up so data and information is archived to allow future replay of logged database activity.
For information about how you can use the information logged in this task to replay database activity, see the Related reference.