Re: Transaction log files in a SE database

I couldn't help but add my two pennorth to sally's excellent comments. There is one thing which most users forget about SE. Any schema change entails - 1. Back up the database 2. Restart logging SE does not log schema changes so if a new transaction involves a slightly different table layout, a different index perhaps But I'm not too usure, than you can't roll it forward. > In article <43i4r4$9cm@centaur.achilles.net> > dean@achilles.net "Dean Steptoe" writes: > <snip> > > We tried to roll-forward the > > database using the logfile, but it DID NOT work. > > I have found a number of things which can stop this being able to > work (in SE): > > i) Not clearing out the '.dbs' directory before restoring the > database from backup. The rollforwards may try to create temp > tables in here which already exist. > > ii) Not clearing the transaction log down in line with the backup > process. It is vital that the backup is taken with no-one > altering the database, and that the transaction log is > immediatly cleared down. > > Have you found more ways of stoppin 'ROLLFORWARDS' working? > > Please tell! > > -- > ======================================================================== > ====Sally Woolrich | This mail contains my > personalsally@excelsis.demon.co.uk | views not those of > my employer!============================================================ > ================ Malcolm Weallans Online Database Consultancy Phone 0628-72154 Fax 0628-37463 CIX - onlinedbc