r u talking about BEST practice?

rather than possible ones? From what i understanding is:

1.you treat database as "data store" which is basically conceptually against relational database.i'm not going dig deeper into this, pls revisit this part by googling or referencing textbook.if your database is intended designed this way,it must be a reason.Immigration to other database is not excuse, my previous company is vendor of product using either sql server/oracle, they still came up different version of SPs/trigger..etc for functionality to gain better performance/avoid security issue..etc.

2."SP can be eliminated completely"--i DO agree,no problem at all. but is this should be recommended or BEST practice, apparently NOT.we treat sp as API and interface of database. anything from "frontend" can interact with db by consuming it.pls bear in mind, most of databases are definitely live much LONGER than "frontend" logic implement by java/c#. platforms come and go,but data remains.

u possibly miss my point, SP is not issue. i'm trying to say, as developer,we should stick to the BEST practice as much as we can, rather than possible ones.

For some reason, we can't approach things this way,like u previous said, DBA respond very slowly... we live with it, and work out a way to get things done in fast/acceptable manner.

Ask urself honestly,

1.r u happy with the approach u r using?

2.how much time u spend on studying (read books/google) database concepts/issues/coding/best practices compare with u doing same thing on JAVA/other language? what's the ratio?

Anyway, thx for sharing ur thought with us, i really appreciate it!