[1] "business logic or domain logic is the part of the program that encodes the real-world business rules that determine how data can be created, displayed, stored, and changed.", https://en.wikipedia.org/wiki/Business_logic
Business logic isn't pulling data from database, how to map an object to a table, or the specific SQL query to grab some data. Those are technical details. SQL should just be pulling, saving and querying from the store without much maniplation. Not changing the data.
It's the rules that a business stakeholder might be interested in creating.
When you start putting the tax calculation rules into the stored proc, thats where the problems begin.
If you create a CTE to pull the information required to perform the calulation then return that info without doing the calculation thats fine.
If you are not allowed to do this kind of things, then what is left? Do you interact with your database as if it were just a bunch of VSAM files?
So in a lot of ways, yes people use databases like they're just persistent memory with indexes.
They're great for storing complicated queries, but the actual buiness logic? No.
Have some stored procs for updating and querying data, then a lightweight abstraction around them in the application.