Frank, Why do you want to include it on all table create statements? I don't think all tables should be, nor need to be created 'not logged initially'. I do like to use it on tables that will become very large, such as fact tables. I believe the primary reason to use this clause is to avoid logging. Given the fact that log files can now be 256 GB for Version 8, I don't think it is an issue for anymore. This being said, I do use it when creating tables that contain millions of rows in case there are big update/insert/delete statements run against it. It is also useful when creating a new table from an existing table with an insert/select statement, such as when columns need to be added or changed. It is also a good way to empty out a table's contents quickly with the 'with empty table' clause in an alter statement. A table cannot be altered later to have this attribute, so I like to use it just in case. Now, the bad part: be VERY CAREFUL when writing the SQL used in the unit of work. If there is ANY mistake in it the table that had not logged initially activated becomes trashed and must be recreated. Even a syntax error will trigger this 'feature'. Hope this helps.
Regards, Steve Mazer Senior Database Consultant Fourth Millennium Technologies IBM DB2 GOLD Consultant At 10:03 AM 2/26/2003 -0500, [EMAIL PROTECTED] wrote: > >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
