Archives of the TeradataForum

Message Posted: Tue, 15 Nov 2005 @ 15:25:59 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Tuesday, November 15, 2005 10:05 -->

Embedding business logic in SPs or macros may be practical from the developer's standpoint, but from the "big picture" point of view they are simply not portable and thus unacceptable as vehicles to implement business logic.

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.

Another problem with SP's and macro is configuration management and version control is difficult to automate and to store. If I had my say on any project, SPs and macros would have no place in the business side and would only be used by sysadmins and dba's to discharge their platform specific duties. My data and process models, along with all business logic shall remain platform/language independent and all SQL would be coded in ANSI formats.

	<Prev	Next>		<<First	<Prev	Next>	Last>>