<No Subject Supplied>

>From naomi Sun May 30 10:58:40 MST 1993 remote from qip From: naomi@qip (Naomi Walker) Message-Id: <9305301758.AA05499@qip> Received: from qip by misty.anasazi.com; Sun, 30 May 93 10:58:42 MST Received: by qip (5.61/1.2) (from naomi (Naomi Walker) to informix-list@rmy.emory.edu) id AA05499; Sun, 30 May 93 10:58:40 -0700 Subject: Re: A question about exporting To: informix-list@rmy.emory.edu (Informix List) Date: Sun, 30 May 93 10:58:40 MST In-Reply-To: <1993May29.214315.24723@osh3.OSHA.GOV>; from "Charles Yamasaki" at May 29, 93 9:43 pm X-Mailer: ELM [version 2.3 PL11] Content-Type: text Content-Length: 1175 > The question: How the heck do I keep dbexport from altering my data? > > Next, the reason why I was looking into this is that a colleague told me > that I should take the very large database I'm working with and unload > and reload it. He said I could increase performance by doing this since > it has been built from an empty database to about 150MB by adding a > single record at a time, and that something to do with indexing would be > defragged (or something like that). > > The question: Can an export-import cycle increase performance? I tend to use tbunload/tbload instead of export/import. This process not only fixes index fragmentation, but stuffs all the rows in one extent (if there is room in the partition). It also retains next extent values. If I remember correctly, a dbschema is used for dbexport, which does not save extents or lock modes. I'm going to use the dbext program Bob Baskett posted to preserve extents (thanks, Bob). -- Naomi Walker (aka N7FSA) naomi@anasazi.com Phoenix, Arizona To get the full value of joy, you must have someone to divide it with. ---Mark Twain