Re: Restores

>> "Cesar Inacio Martins" <cesar_inacio_martins@yahoo.com.br> wrote in >> message news:mailman.53.1269437682.1071.informix-list@iiug.org... I don't know if the onunload/onload have the same version limitation of ontape, did you tested it? AFAIK they works in a similar way from ontape, dumping the used pages and the structure of the table/indexes... what is very fast, just like the ontape. And with it , you can specify to export the database in single command to unique file... >> Just remember, the destination must have the same dbspaces >> configuration... and if your company buy the workgroup before feb/2009 >> tables use partitioning , you will violate a license limitation on the WG >> (don't permits pa I may come to regret this but ... I don't agree with you at all! I haven't tried onunload/onload in this case to see if it too is affected by the EE->WGE irritant ... But even if they work, onload/onunload have been notoriously bug-ridden in previous releases, to that extent that, a few years ago, if onload was the answer, all you could infer was that it was a stupid question .... ;-) But, assume that most of the onload bugs have been fixed now - although the one whereby the -d index is ignored for indexes is still there - it's much, much, much, MUCH slower. I don't exactly how it works but with onload you see a lot of reads interspresed with the writes; I assume that some kind of pre-write space chekcing is going on.