 |
 |
Archives of the TeradataForum
Message Posted: Tue, 15 Nov 2005 @ 17:21:49 GMT
| Subj: | | Re: Stored procedures results |
| |
| From: | | Victor Sokovin |
| | SP's or macros are difficult, if not impossible, to model and can't be generated by a CASE tool. The key to reusability is not small
packaging or elegant solutions hidden in SPs and macros. The key is to model both data and processes and build everything in CASE tools and
portable languages, that way the human investment is reusable in other platforms and makes it easier for the organization to drop one technology
and adopt a new one on the fly. In my previous engagement, I saw the organization come down to a halt because they coded everything on SPs.
When the organization reached the RDBMS limits they were, for all practical purposes, done for good. A very painful and expensive
lesson. | |
I think this is still science fiction. CASE tools as we know them today are not even able to store table definitions. But if you want
kilometers of auto-generated code, just try Oracle Designer. It creates packages in PL/SQL.
Reality is that vendors have done everything to make migrations as difficult as possible. CASE tools won't help to change that. I don't think
that the decision to use or not to use SPs should be made on the basis of their cross-vendor portability. SPs are not portable, period.
Regards,
Victor
| |
