I recently wrote some macro's but am now considering porting to the code to stored procedure's considering macro's are a single transaction and could be very expensive in terms of rollback if yiou have lots of inserts in them.
As for stored procedures , talking in TD 13 context, is it still bad on performance ? As in doesnt utilize parralelism ? row by row operation ?
If i am selecting from a source table and inserting into a table, will it select one row at a time ? or will it go for multiple rows ?
>>"As for stored procedures, talking in TD 13 context, is it still bad on performance ?"
And you are saying this because...
>>"As in doesnt utilize parralelism ? row by row operation ?"
It depends on the code you write...
>>"If i am selecting from a source table and inserting into a table..."
If you are doing this and you are not using INSERT...SELECT the problem is you, not Teradata (or Oracle, or whatever).
>>"... will it select one row at a time ? or will it go for multiple rows ?"
It will select one row at a time if you are using a cursor loop. It will go for what you call "multiple rows" if you use INSERT...SELECT.