Thats why I said its a waste of time for test installations and should be optional and enabled by default :) If I don't care if my test database works after a crash or not I don't need a backup. Just imagine you play around with loading/unloading large databases with repm and just want to know if it works and your client software works and not actually doing it in a productive scenario. Beeing forced to do a backup in these scenarios after each and every load is annoying and takes alot of time for nothing.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Freitag, 6. Dezember 2002 12:09 > To: Warga (ext_Zip) Marco; '[EMAIL PROTECTED]' > Subject: Re: Table is read only! > > > Hello, > On Freitag, 6. Dezember 2002 09:36, Warga (ext_Zip) Marco wrote: > > I also ran into this error before. > > Why is it that one is *forced* to do a backup after a load? > > I mean if I load a database for test reasons a full backup > may just be > > a waste of time. > > > > I would suggest do make this "feature" optional and enabled by > > default, not mandatory. Or is there a technical reason? > > > loading is so fast because it does no logging. > So you have to do a backup afterwards or you will never be > able to proceed > with anything like recovery if you DB crashes. > > Peter Willadt > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
