We started leveraging SQL very heavily in our application so that business people can customize app behavior without bothering developers. We are getting close to 100% config-only coverage using SQL.

We tried rolling our own scripting language and other ideas, but we decided that we weren't ever going to catch up with the level of testing & validation that SQLite has achieved with any amount of in-house resources.

Once we embraced SQLite, we found an entire universe of capability. Here is one of the comments I made just yesterday about this kind of thing:

  https://news.ycombinator.com/item?id=27362708

Using SQL to get reports and analyse existing data, or to actually create schemas, change data, maintain transactions over related changes and so on?

Yes since it is describing more what you want and less how to do it, but SQL is not an end-to-end solution.