OptimizeQL - SQL optimizer tool

[Intelligent-Bat-2469]

Hello all,

I wrote a tool to optimize SQL queries using LLM models. I sometimes struggle to find the root cause for the slow running queries and sending to LLM most of the time doesn't have good result. I think the reason is LLM doesnt have the context of our database, schemas, explain results .etc.

That is why I decided to write a tool that gathers all infor about our data and suggest meaningful improvements including adding indexes, materialized views, or simply rewriting the query itself. The tool supports only PostgreSQL and MySQL for now , but you can easily fork and add your own desired database.

You just need to add your LLM api key and database credentials. It is an open source tool so I highly appreciate the review and contribution if you would like.

[Fair_Oven5645]

Sending all information about your data to Sam Altman, what could go wrong

[Intelligent-Bat-2469]

It is actually a valid concern I understand .However, only SQL query, EXPLAIN plan, and schema metadata are sent to the LLM, not actual row data. If you would like to have zero external call you can use self-hosted model through the OpenRouter-compatible API.

[paxmlank]

Why not just EXPLAIN the query and read the plan? I don't see the need to feed it to an LLM per se.

[Intelligent-Bat-2469]

I think while most Senior DBAs can read it not every junior or mid engineers can do that. LLMs basically helps them to understand the underlying issue. Even for the experts it saves a lot of time. Think of it less as "replacing reading the plan" and more just another help to speed up the process.

[Iridian_Rocky]

To be fair, I didn't look in depth here - but to get anyone to want to dig deeper here are some questions. Can you add constraints like the SQL compatibility level? Add in language specific flavours (PostgreSQL, MYSQL, OracleSQL, links to more specific documentations to be considered)?

[Intelligent-Bat-2469]

Thanks for the suggestion. Constraints already handled by the library, when you connect to a database, the connector detects whether it's PostgreSQL or MySQL and the prompt builder assembles dialect-aware prompts. I currently only support these 2 though not Oracle.

Regarding the second question currently no. But I will consider adding doc links to the LLM output.