RE: ROWIDs and fragmented temporary tables

Is there a quick fix? No. Your problem has nothing to do with temp dbspaces. Be aware, if you create tables with rowids, you are simply generating a unique number (serial value - no intelligence). Performance will be impacted, as well as storage. This may not be an issue with temporary tables, but may on large tables. Scott H. > -----Original Message----- > From: com@netinfo-moldova.com [SMTP:com@netinfo-moldova.com] > Sent: Monday, November 15, 1999 3:30 AM > To: informix-list@iiug.org > Subject: ROWIDs and fragmented temporary tables > > Hello, > > > I have a question regarding ROWIDs on fragmented temporary > tables. I've just installed and configured an Informix server (7.30) > and I configured it to use three temporary dbspace. > I've got a surprise discovering that some of applications > use rowid columns on temporary tables. As a result of using > more than one temporary dbspaces the temporary tables > got fragmented and these applications end up with an error > stating that there are no rowids on fragmented tables. > > Is there any ways to handle this issue quickly (Informix Server > parameter on env. variable) ? Of course for now I've > listed just one temporary dbspace in DBSPACETEMP onconfig > parameter and if we'll have to we'll rewrite the application > so it will not use rowid's on temporary tables, but I'm wondering > wether it is a simpler sollution. > > Thank you, > Octav > > > Sent via Deja.com http://www.deja.com/ > Before you buy.