Teradata table schema for output data tool
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
KevinSobel
6 - Meteoroid
09-07-2022
12:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
In Designer, I have a workflow using a Select tool. The columns look like this:
Shortly after this, I use the Output Data tool with Teradata Bulk Loader to push the results to a table, and the Output tool is configured to drop and then load the table.. However, on the Teradata, the table is being created with a different schema than is being shown in the Select tool. For example, FNAME is being loaded into the Teradata as a CHARACTER(100) field instead of a VARCHAR(40). The name then gets uploaded, and then null-padded out to the full character width.
Why isn't the bulk loader respecting the schema in the Select tool? Where is the schema configured for the table creation?
Labels:
- Labels:
- Database Connection
2 REPLIES 2
17 - Castor
09-08-2022
05:12 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @KevinSobel ,
can you confirm that the table currently in Teradata has CHARACTER(100) for that field?
If so, it looks like it's re-creating the same table format as what is being dropped. You could try getting around this by using a pre-SQL statement in the output tool to drop and create the table, then outputting this way:
You can read more about using pre-SQL statements here:
M.
09-08-2022
06:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The table definitely has CHARACTER(100), and the table also does not exist before the job is run unless we have to re-run the Alteryx workflow for some reason. It’s a brand new table being generated each month, with a different name containing a date code (“TABLE_YYMM”, so “TABLE_2208”, for example.)
