Versioning data in SQL Server so user can take a certain cut of the data

I have a requirement that in a SQL Server backed website which is essentially a large CRUD application, the user should be able to 'go back in time' and be able to export the data as it was at a given point in time.

My question is what is the best strategy for this problem? Is there a systematic approach I can take and apply it across all tables?

5
задан Mark Robinson 7 March 2011 в 14:14
поделиться