Transaction Logging - pros n cons

Dear other_netters: We currently use transaction logging in our development environment while we check it out. In the past 8 months it has worked reasonably well as long as nobody does something silly like "LOAD FROM ... INSERT ..." on 12,000,000 4k rows. Another project I supported ran such an instruction a great deal and gave me many headaches with long transaction errors. Several time it crashed their engine to a degree where it could only be repaired by restoring from archive. We are currently discussing Disaster recovery and the place of transaction logging in this scheme. Transaction logging will restore your data to the last good transaction - but it increases the risks of crashing the system if somebody does something silly. What I would like to hear are your comments on whether you use transaction logging or not and whether it has caused problems or solved them. If there is sufficient interest I will post the results. Please note that we have a great deal of control over who writes what instructions against the engine, but there is no protection against ourselves. My co-workers express that they are prone to failure and may inadvertently do a "LOAD FROM ... INSERT ......" on The Big Table by mistake in 6 months. j. _____________________________________________________________________________ Jack Parker - Contractor | Hewlett Packard, BSMC Boise, Idaho, USA| I've forgotten more than jparker@hpbs2561.boi.hp.com | I ever knew (208) 323-5388 (W) (208) 384-1623 (H) | _____________________________________________________________________________