RE: Role of DBSPACETEMP
Posted in 2000
Topics: Storage & Space Management, Security, Permissions & Auditing
We had an application that created temp tables without the WITH NO LOG and the temp tables were created in rootdbs. Our solution was to use regular (non-temp) dbspaces in the DBSPACETEMP list and that was used to store these temp tables. > -----Original Message----- > From: a_blonde@mindless.com [SMTP:a_blonde@mindless.com] > Sent: Wednesday, January 05, 2000 9:18 AM > To: Henk van der Geld > Cc: comp.databases.informix > Subject: Re: Role of DBSPACETEMP > > ---- you wrote: > > Hi, > > > > We have some questions about of the role and the effect of the envvar > > DBSPACETEMP. Sometimes I read that in databases that are logged, > > temporary tables are logged by default and WILL NOT BE CREATED IN > > 'DBSPACETEMP'. In that case it is necessary to use the WITH NO LOG > > option of the CREATE TEMP TABLE statement. Our experience is that temp > > tables > > without the WITH NO LOG option will be created in the root dbspace. This > > > > may cause the root dbspace to be filled up. Understanding the above the > > DBSPACETEMP will have no effect when database is logged. How can I get > > around this and force that temp tables are created in the database space > > > > of my choice? Anybody who can clearify this? > > If you mean you cannot change the source code, then you are stuck Dude! > > For logged databases, if you use CREATE TEMP TABLE, they are created in > the dbspace where the database resides. If you use INTO TEMP they are > created in the rootdbs dbspace. > > The only way to change this is to use the WITH NO LOG syntax Dude. > > AB > ---------------------------------------------------------------- > Get your free email from AltaVista at http://altavista.iname.com