Not a great example, and the Person table is not normalized. Building up a description to display is not even what I would call business logic. Some business lo

Not a great example, and the Person table is not normalized. Building up a description to display is not even what I would call business logic. Some business logic naturally belongs in the database, some doesn't. Limiting the RDBMS (not SQL) to CRUD operations throws away too much. What the article describes is the opposite of 40 years of enterprise-scale experience with RDBMSs. Think about a database that supports multiple applications written in different languages at different times by different teams. The problems with implementing business logic at the application level are more obvious then -- violation of the DRY principle, for one.