It does not hurt to have it the create statement. Actually, it gives you the option to do not logged operations in the future. If you do not add the option at create time then you must drop and recreate the table to add this option to the table.
We use it on a limited basis but the option has proved to be highly useful and has significantly improved performance on mass updates and inserts. -----Original Message----- From: Fortier, Christi (GTS) [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 10:25 AM To: '[EMAIL PROTECTED]'; Fortier, Christi (GTS) Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: [DB2EUG] RE: NOT LOGGED INITIALLY BIG one!!!! If you have any referential integrity constraints on your tables you will not be able to alter them if you have "not logged initially". You can drop them but will not be able to add them again unless you recreate the table. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 10:03 AM To: Fortier, Christi (GTS) Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: NOT LOGGED INITIALLY We are having a debate here as to weather or not to include the NOT LOGGED INITIALLY clause on all our table create statements. Would others who have made a decision one way or the other please share why they decided for or against. I appreciate everyone's response. Frank - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
