Lynn Pettis (3/11/2013)
In addition, if the underlying table structure changes but the output of the stored procedures remains the same, you isolate the changes to the database. You modify the stored procedures to use the new table structures ensuring that the input and output of the procedures remains the same, the application does not need to change.
Replace "stored procedure" with "C++ procedure" and swap "application" with "database" and you get a perfectly valid statement again.
If you work with s.p., you isolate the changes to the database. And this can be good if you don't want to change the application.
If you work with the application language, you isolate the changes to the application. And this can be good if you don't want to change the database logic (or even don't want to have logic at all in the database).
DBAs obviously tend to prefer s.p. because they are accustomed to them.
Developers should prefer to avoid s.p.