Re: Crashes? Could it be this???

Keith L Morris wrote: > > On an application we have here at work, the original developers set > things up to create a NEW table for each process that is run and the > table has ONE row in it. > > We run 100's of processes per hour. So each hour we have 100's of new > tables being created and deleted. > > We also have problems with this database crashing and becoming majorly > corrupt. > > My GUT LEVEL instinct is that the ONE TABLE with ONE ROW per process is > NOT a good thing..... Informix has spent a lot of time making the > database bulletproof for ROW insertion/deletion/update. They also make > sure that TABLE creation/deletion WORKS.... but my "instinct" would be > that they probably DON'T TEST creation/deletion of complete tables on > such a scale. > > I would like to convert this code to have ONE table and a row in it > PER process. I think this could solve SOME of the crashes and > corruption problems. > > Anybody have any ideas or experience on this? Or am I just barking up > the wrong tree...... It's certainly a tree to be barked up, but not necessarily the one to solve your crashes. IMNSHO table maintenance is best left until scheduled maintenance time, not during production time. As you say, databases are designed to maintain rows, and lots of them. So I would go along with your idea. As to your problem, what database server? What version? What platform (Box, config, OS, etc.)? What version? What tools? What version? Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@mydas.freeserve.co.uk |//////// /| | http://www.informix.com http://www.informixhandbook.com |///// / //| | http://www.iiug.org +-----------------------------------+//// / ///| | |This email will self-destruct in |/// / ////| | |10 sec. If you received this email |// / /////| | |in error, sorry about the mess. |/ ////////| +----------------------+-----------------------------------+-----------+