Re: Database Design: Maintain Audit Trail of Changes

On Thu, Jan 3, 2013 at 2:50 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
>
>   There should not be many changes in these tables.

Ok.
 
>
> And historical data
> cannot be purged or the purpose of maintaining a history is lost. The
> history is valuable for tracking changes over time in regulatory agency
> staff and to prevent data manipulation such as was done several years ago by
> the president of Southwestern Resources (a gold mining company) to pump up
> the company's stock price by changing assay results.

I understand it and for this reason I said to "use some strategy to purge old historical data *OR* make your audit tables partitioned"... 

regards,