Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Teradata Bulk Loader behaves differently between the Output Data and Data Stream In tools

KevinSobel
6 - Meteoroid

 

I am loading a 1 column table with 160M rows into Teradata using Teradata Bulk Loader. If I use the Output Data tool, it takes 1 minute. If I use the Data Stream In tool, it takes 18 hours. Can someone explain why the difference between the 2 tools? I would prefer to use the Data Stream In tool as I want to use the data loaded to join to another table in Teradata.

 

Also, my DBA is curious why when using the Data Stream In tool the workflow is only using 1 processor when we have 16 specified for number of sessions (AMPS).

 

Attached are screen shots from the 2 workflows.

 

Thanks,

 

Kevin

 

 

 

 

0 REPLIES 0
Labels
Top Solution Authors