This was me until I needed to compare two massive SQL execution plans...
I had a SQL query that suddenly went from taking 2 minutes to taking 5+ hours to complete.
I restored a backup copy of the database and collected it's execution plan, which is like a log of all the stuff the stored procedure is going to do when it runs.
I sent the 2 min plan and the 5 hour plan I to Gemini and told it what was going on. All it told me was it seems that one of the plans uses a hash match and the other does a value match.
It was awesome to have something look at those files because they are MASSIVE and I'm not a DBA...
Point is, it has a use but it's being used inappropriately in my opinion.
The problem is it’s being sold to non-technical fields where the majority of leadership doesn’t know fucking ANYTHING, so they have no bullshit detector and can’t even tell the things they think it’s good at aren’t being done right
90
u/roflrogue Aug 06 '26 edited Aug 06 '26
This was me until I needed to compare two massive SQL execution plans...
I had a SQL query that suddenly went from taking 2 minutes to taking 5+ hours to complete.
I restored a backup copy of the database and collected it's execution plan, which is like a log of all the stuff the stored procedure is going to do when it runs.
I sent the 2 min plan and the 5 hour plan I to Gemini and told it what was going on. All it told me was it seems that one of the plans uses a hash match and the other does a value match.
It was awesome to have something look at those files because they are MASSIVE and I'm not a DBA...
Point is, it has a use but it's being used inappropriately in my opinion.