Hi everyone,
I've shared this on here before, but it applies again here. At a previous employer we used triggers to track the changing of all fields. Old values and new values were stored. There is OBVIOUSLY going to be a time cost with implementing such a technique, but it's really a business logic or business need question. If your system crashes at 5PM, how much does that cost you to have to revert to, for example, midnight the previous night as your most recent snap shot of the data? Sadly, our purpose was less noble. We had to find out what the fat fingered, and either lying or forgetful end users were REALLY doing when they alleged the system did something that it really did not. Honestly, the performance hit was not that significant either... especially considering the payoff of actually HAVING that data.


>would it be a big deal to have an exact second copy of the table and update both one after the other so you are always no more than a record behind as regards a backup?
>Slán
>~M
>
><snip>
>>
>>2) What experience do folks have with continuous backup possibilities (or hourly etc.)?
>>