> Neil Conway > On Fri, 2004-10-22 at 07:54, Simon Riggs wrote: > > If I could go further, I'd like to add this as an option on the command if > > possible, rather than a presumption that all such statements should not be > > logged. > > Why is that necessary? >
So you can choose whether to do this or not. IMHO, it is important to have the optimization, but it shouldn't be the case that EVERY statement is forced not to log. If I risk data loss, I'd like it to be my choice to do this. This effects COPY and CREATE INDEX also, though I know you aren't working on those at present. I will implement thos eif tyou do this for CTAS. DB2 supports this as a user option via NOT LOGGED INITIALLY http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/admin/c0006079.htm Oracle supports this as a user option via NOLOGGING http://www.devx.com/dbzone/10MinuteSolution/22191/0/page/3 (The Oracle manuals aren't available online) Teradata also supports this... These are quoted only to show that others have found this a useful optimization, not because I believe we should slavishly follow others in their syntax. Tom's view previously was, IIRC, that you can do this with a Temporary Table, which is true, but that isn't very helpful when you actually want the table to be permanent. Best Regards, Simon Riggs ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
