Archives of the TeradataForum
Message Posted: Tue, 22 Oct 2002 @ 18:54:32 GMT
| Subj: | | Re: Producing large extract files |
| |
| From: | | Geoffrey Rommel |
| | Attached is what I tried with FastExport. Perhaps you can advise me as to what's wrong with the parm settings. I see that you said
to use a FORMAT of BINARY and a MODE of RECORD for example. Anything else? | |
I don't think anything is wrong with your script. FastExport will produce a fixed-format file, but only if every expression in
your select statement produces a fixed-length field -- hence my previous remarks about casting things to fixed-length. If you don't do that,
every case expression will come out as a varchar preceded by a two-byte (short int) length.
There are two modes: indicator and record. Mode indicator puts extra bytes on the front of each record in which the bits correspond one
for one with the remaining fields; mode record does not. If a bit is on (1), the field is null. If I've read your SQL correctly, you are
exporting 33 fields, so you'll get 5 indicator bytes.
As for the formats, they aren't quite what you might expect. The only difference between fastload, binary, text, and unformat is whether
they put a record length and/or an end-of-line character in the output record. Unformat adds neither, so maybe it would be your best
choice.
Fastload: record length; EOL
Binary: record length; no EOL
Text: no record length; EOL
Unformat: no record length; no EOL
| 
