 |
 |
Archives of the TeradataForum
Message Posted: Fri, 24 Sep 2004 @ 16:14:03 GMT
Subj: | | Re: ETL Approach Recommendations |
|
From: | | Anomy Anom |
<-- Anonymously Posted: Friday, September 24, 2004 12:10 -->
I would agree that Teradata Stored Procedures are not inherently slow, and can add a lot of value. But what I have seen is a tendency for those
writing SPs to use CURSOR (serial row-at-a-time) processing and procedural logic. For large volumes of data, that does tend to be dramatically
slower than SQL "set processing" which can take advantage of the parallel nature of Teradata.
| |