Let’s talk Alteryx Copilot. Join the live AMA event to connect with the Alteryx team, ask questions, and hear how others are exploring what Copilot can do. Have Copilot questions? Ask here!
community Alteryx IO MyAlteryx
alteryx Community
Search
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Close
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
‎11-16-2023 12:04 PM

 

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

 

 

 

 

Preview file
169 KB
Preview file
174 KB
Reply
0 Likes
0 REPLIES 0
Copilot AMA
License admin COmmunity Live
Labels
Top Solution Authors
View All