Can you not use EXPLAIN ANALYZE to identify steps that had the highest compute time? I think most databases have some form of this.
replyThis is a great command everyone should know. We once had a long running database query that was blocking a pipeline (code was written in a week and of course became integral to operations). Ran it, 15 minutes of thinking, added a new index on an now important column, and cut the run time down from almost 30 minutes to 5 seconds.
replyI've never heard of this, and I'm pretty sure my coworkers haven't either. Thanks for mentioning it!
replyhttps://chatgpt.com/share/68104c37-b578-8003-8c4e-b0a4688206...
You're onto the original idea I started out with! Unfortunately it's very difficult to correlate input SQL to an output query plan – but possible. It's definitely in future plans
replyMSSQL has the execution plan thing that will tell you which steps are involved and how long they take.
reply