in reply to Re^3: No stored procedure bashing on my watch!
in thread Recoding a multi-sql-statement storedProc transaction in a script

Well, what the heck are storeprocs other than an "unknown number of programs?"
They are a known number of programs, all written in the same language, and stored centrally. Given a database, it's very easy to extract out all its stored procedures - and its quite easy to find out which tables each stored procedure touches. But if the SQL is scattered around over many applications, written in a myriad of languages, all running somewhere on the network (and for some organizations, the "network" can consist of thousands of machines), it's much harder to get everything updated if the schemas change.
  • Comment on Re^4: No stored procedure bashing on my watch!

Replies are listed 'Best First'.
Re^5: No stored procedure bashing on my watch!
by punkish (Priest) on Dec 17, 2004 at 13:08 UTC
    and so is a finite number of Perl scripts with SQL "scattered" around in them a known number of programs, all written in the same language, just happened to be stored "externally."

    There are many conditions in which the argument to access everything via storedProcs would apply, but there are many conditions in which not to do so would also apply.

    case closed.