How about adding indexes and stats on the appropriate columns, and have look at your execution plan while you’re complaining. Bushels of low hanging fruit are ready to be picked for devs who bother with a little SQL performance tuning.
And if doing pagination, order by an index and add a minimum bound, instead of doing LIMIT 5000,5000.
Oh and if the query optimizer picks a bad index for what you’re doing, you can force a better one.
And don’t do dependent subqueries and…
Idk, this is stuff I learned in my first year or 2 at my first job in the field. And I’ve had people on reddit tell me I’m a programmer not a software engineer because I don’t have the education so therefore I can only be a code monkey. Yet somehow Amazon pays people 5x my salary to not know how to use SQL efficiently while I’m out here building queries that show no non-index reads, sometimes in databases where I’m not even allowed to add new indexes because of legacy reasons.
How about adding indexes and stats on the appropriate columns, and have look at your execution plan while you’re complaining. Bushels of low hanging fruit are ready to be picked for devs who bother with a little SQL performance tuning.
But that’s work! How dare you ask me to do work!
And if doing pagination, order by an index and add a minimum bound, instead of doing LIMIT 5000,5000.
Oh and if the query optimizer picks a bad index for what you’re doing, you can force a better one.
And don’t do dependent subqueries and…
Idk, this is stuff I learned in my first year or 2 at my first job in the field. And I’ve had people on reddit tell me I’m a programmer not a software engineer because I don’t have the education so therefore I can only be a code monkey. Yet somehow Amazon pays people 5x my salary to not know how to use SQL efficiently while I’m out here building queries that show no non-index reads, sometimes in databases where I’m not even allowed to add new indexes because of legacy reasons.