Looking at all the answers to the question: "Are the days of stored procedures numbered".
It appears as if some people are jumping in with strong opions based on what I perceive to be a narrow range of software development experiences.
I would like to re-submit the question, but first I need help putting together a list of qualifications required before answering.
Here is one version of the requirements to get you started.
- Worked on one large database like for ever (10+ years).
- Starting some time in the 1990s went to work for a startup with the goal of creating a world beating ERP system.
- Wrote code in either VB6 or Cobol.
- Released new versions of said system once every 2+ years.
- Came in as new developer of said system and had good the fortune to be allowed spelunk through thousands of lines of stored procedures so that some major changes to business logic could be implemented.
- Worked deep in the bowels of a Financial institution adding web based front ends to various parts of large mostly ossified database.
- Wrote more SQL code than many .NET developers have written C#.
Etc.