|
Archives of the TeradataForumMessage Posted: Sun, 17 Jul 2005 @ 11:15:53 GMT
Hi, No, you don't face any such (technical) limitation, although for practical purposes you wouldn't be the first person I've come across to work within those rules. What you have to remember is that the DEFINE and SET RECORD statements MUST define the layout of the input record. How the input records are created and from what type of data source is totally irrelevant. The FASTLOAD format is simply a convenient and easy way of matching data types from a Bteq Export/FE to a Fastload job. As an example, if you have a numeric field which is stored in the input record as a signed, two-byte binary integer, then you'd define that field as SMALLINT. Which utility or programming language produced the file and from what type of data source is (as I said earlier) totally irrelevant, you would always code this field definition the same. The VARCHAR data type is a requirement IF you use "SET RECORD VARTEXT", but otherwise is only required if you have variable length character fields in your input record. Hope that helps. Cheers, Dave
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||