[Mr. Jeeves]

Stored procedures should only break in the event of database table or structure changes - with a well-designed relational database those kinds of things should be rare occurrences. But it depends on the application - mine was finance and data structures didn't change much, if ever. They were largely used to drive reporting - all the data was there, so if a report needed to be changed or retired usually only one stored procedure was affected.

I did all the work myself, so it was easy to keep control. In a larger, team environment there are certainly reasons to compartmentalize the business logic differently - not least so that each little Indian H1B has a gig in perpetuity. :)

[csivils]

In “modern” development, they move more and more to the front end/web server in the name of efficiency... but over time, I have noticed that it takes longer and longer to do anything... both to code it and for it to run.

Amazing how the word efficiency doesn’t seem to mean what I think it means :)