Re: Unloading to two destinations

Posted in 2005

Topics: Migration, Import/Export & Data Conversion

Andy Kent — 12 Jan 2005 03:58:17 -0800 — source: Usenet: comp.databases.informix

That would be the obvious one, but it incurs a lot of i/o. The whole of the existing table would need to be written to the two other tables and then one of those would need to be unloaded. (The purge amounts to about 50% of the table). I was hoping to find some way of unloading the data directly from the old table. Andy

↪ replying to Andy Kent

Richard Kofler — Thu, 13 Jan 2005 09:20:56 GMT — source: Usenet: comp.databases.informix

Andy Kent schrieb: > That would be the obvious one, but it incurs a lot of i/o. The whole of > the existing table would need to be written to the two other tables and > then one of those would need to be unloaded. (The purge amounts to > about 50% of the table). > > I was hoping to find some way of unloading the data directly from the > old table. > > Andy > read the FM about table fragmentation and detaching of fragments. This can/will do your job & is pretty fast, once your table is fragmented and when you have multicpus & some memory to throw into the job and using PQDPRIORITY dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe