Additionally learn stored procedures.

Helps simplify complex SQL queries and no need to waste network traffic on data that client side is never going to use, and waste CPU cycles processing it.

Yes, what about database portability?

I am on my 50s and it only mattered on a single project, which was anyway a middleware for application servers.

▲

duckmysick 14 minutes ago | parent | next [-]

I moved from stored procedures to dbt. I find it easier to maintain and it helps me with version control, testing, and docs. Plus, since I deal with data pipelines a lot it get other goodies like lineage and auto DDL.

▲

EvanAnderson 4 hours ago | parent | prev [-]

> Additionally learn stored procedures.

For sure, but have a solid grounding in set theory to go with it.

I've dealt with so many poorly-performing stored procedures that ended up being written as iteration over a CURSOR when they could have been done with sets. Programmers who don't grok set theory reach for iterative constructs which, while they work fine, are an impedance mismatch with SQL.

	▲	clappski 4 hours ago \| parent \| next [-]
		At least in that case you can refactor the stored proc to be more performant without pushing application changes.
	▲	pjmlp 3 hours ago \| parent \| prev [-]
		Agreed, however that applies to SQL in general. I have seen DBAs make wonders without changing queries, only by adding the right set of indexes.