Teradata table schema for output data tool

[KevinSobel]

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?

[mceleavey]

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:

https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Alteryx-Pre-Post-SQL-Statements/ta-...

M.

[KevinSobel]

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.)