If performance is essential, then I agree that stored procedures are going
to win, but in my experience it is not without major trade-offs.
I once worked on a large business critical project where all business logic
was in stored procedures, due to the reasons you have addressed above.
Some of
I think you're the first person that has brought up the desire to change
databases in the last 10 years! Virtually no one ever changes relational
database management systems these days once the decision has been made.
Having the business logic in the database also tends to get around issues
with
When this topic came up a few months ago, my final statement was that after
years of indecision I finally arrived at a pattern I like: I prefer to use
procs at the barrier between the service layer managed code and the
database. My procs only do "database stuff" (I hope you know what I mean)
...
