Advantages of TPT over the legacy Stand-alone load tools:
1. Scalable loads on the client load server
If the bottleneck of the load job is the I/O reading the data files or the CPU used by the load job, TPT can scale multiple processes to overcome the bottleneck. With TPT, Teradata offers a fully scalable load solution on the client load server and Teradata Database to meet the service level agreement for a load job.
2. Superior Integration with commercial ETL tools
TPT has an API built for commercial ETL tools to use to scale load jobs and for a tighter integration with more control of the load job for the ETL tool. We highly recommend that you use one of the top ETL tools that integrates with Teradata.
3. Many ease of use features (too many to list here)
4. The legacy Stand-alone load tools are stabilized with no new features being added. All new features go into TPT. Customers should freeze their use of the legacy Stand-alone load tools and use TPT for all new load application development. The ETL vendors are using TPT.
Those are a few advantages off the top of my head and there are more.
Sorry Everyone, for putting up this post here as i was not sure of where to put.
I am trying to move a table from teradata to a flat file,my present working env is hadoop env, here i have the script file , but i moved this to TD env so as to run the tbuild -f script_name cmd.
Now my question is, is there any way of executing this very script from any env, by providing the login credentials of TD.