Re: About my latest Question (lock temp table)

Yes, you are correct if you mean making lock irrelevant for table concurrence (deadlocks) error processing on that table. The temp table is only accessible to the user who creates it. Yet, creating it with NO LOG from a DBA point of view also insures that the creation of this table will not write this information to the log file. Being the DBA may not know about this table it could cause a possible log file overflow. Since, this is a "TEMP TABLE" only existing during the life of that process (program) and owned by the person running that process. ------------------------------------------------------------------------- Cheryl Kendricks Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov DTSI, Inc. Database Administrator - DOL Job Corps San Marcos, Texas ------------------------------------------------------------------------ On Wed, 25 Sep 1996, Douglas Wilson wrote: } I think we just did this one, but here goes; } the syntax should probably be: } > create temp table tt } > (aa any_type) WITH NO LOG; } } unless you would like to be able to rollback work on the temp } table itself. } } But there is still no reason to lock a temp table because (someone } please tell me if i'm wrong) the process that creates the table is } the only one which can reference it, making locks irrelevant. } } } -- } Sincerly, } Doug Wilson(dougw@amgen.com) } *** The opinions expressed here are my own and not neccessarily *** } *** anyone elses **** } *** Disclaimer: These are the opinions of the poster not Amgen Inc.*** }