When an architect dings the new guy’s code review because he didn’t include a change log in a new stored proc because the change log helps support people track changes in the code, then you realize that SQL is king at your organization and will be for a very long time.

The logic will always be in SQL.

The application will always take many trips to the database, because all roads lead to Rome.

No matter what. Object-oriented programming, MVVM (MV*), Agile^(tm), functional, whatever. The natural resting position will always be SQL, for all things except the UI.

And possibly even the UI, if we start generating HTML in SQL, which would not surprise me.