Tanel Poder @tanelpoder.com · Mar 13

Reasons why SELECT * is bad for SQL performance: An old blog (with Oracle-specific examples) with a whole range of reasons why. It's not only about network traffic and SQL plan execution, but client side processing and memory usage as well. tanelpoder.com/posts/reason...

21 likes 4 replies

?

Replies

Jon Stone · Mar 13

Dont they say, "never do that" at school?. I would think this would simply get rejected on most decently configured production db. Like it would bounce back and tell your manager?

Quade · Mar 13

Aren't there security implications too?

oscar · Mar 13

interesting - knew a few of these, but there's many more that I didn't lol

@thewatcherknight.bsky.social · Mar 13

You know, I used to do some basic SQL stuff back in the early 2010s and I will say that "Select *" was often the only way to pull all database information to determine what the better command was. Is there a better way to do that now?