 |
 |
Archives of the TeradataForum
Message Posted: Tue, 15 Nov 2005 @ 10:50:18 GMT
| Subj: | | Re: Stored procedures results |
| |
| From: | | Victor Sokovin |
I recall that when Oracle were pushing SPs on the market one of the main arguments they used was that the code was stored *in* the database,
which had a dual advantage: you could either make it static and secure by only allowing (business) users to execute it with different parameters
(validity of which could be checked by SPs) or, alternatively, share it between users (for instance, DBAs) who would like to have a common version
they could edit and see changes done by others. Comfortably, without leaving the DB.
The ability to store the code in the database had appealed apparently. But then again what do you store there? Raw SQL with a bit of
convenient dynamic procedural cosmetics or Visual Basic like outbursts of programmers who can't let go of their procedural past and keep producing
thousands of rows without thinking about performance or maintenance of their creations?
Regards,
Victor
| |
