Re: Crashes? Could it be this???

Keith, I agree with your "gut level" reaction! This is crazy! But in order to advise as to corrective action you will have to tell us more about your environment and what these table(s) are doing for you. Later, At 05:22 PM 7/5/00 +0000, 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...... Thanks, --keith keith.l.morris@wcom.com Mark Griebling mailto:mgriebling@acm.org