Thanks for the quick response. I understand what you are saying and agree to a certain extent. But take it for what it's worth...my opinion is that TPT would benefit from providing a standard set of operational metadata (logs, stats, etc...), whether it's being used in a "script-based" mode or as part of TPTAPI. This would provide operational consistency for Teradata utilities and make support simpler, similar to the idea of creating TPT in the first place to replace all of the seperate legacy utilities we used to have (for which support was unique to each one).
A lot of shops today use third party ETL tools such as DataStage or Informatica. If the support for Teradata is different on DataStage vs. Informatica lets say, you could have confusion and frustration on the part of the end users. Beyond that, if ETL vendors choose to make Teradata support difficult, it makes Teradata look like the "bad guy" and it's hard to prove otherwise sometimes. Providing one consistent view of operational metadata could provide Teradata with ammunition/disclaimer in those cases.
I'm not saying that you force ETL vendors to adopt this either. I'm just suggesting that you make it available. That way, the vendor will also have the flexibility to enable or disable this feature. Then let the end customer decide what is easiest by experience and education...
Just my 2 cents...thanks.
↧