r/dbForge

I need a MySQL client that doesn’t panic the second a table gets bigger than a demo database. Small stuff works fine almost everywhere. The problem starts when you open a large table, run a heavier join, or try to filter results, and the UI suddenly acts like you personally offended it.

Mostly looking for something boring and stable: queries, filters, readable results, basic table browsing, no random freezing.

How do you usually handle large datasets in MySQL? Do you rely on your IDE for browsing/filtering, or do you avoid opening big tables directly and work mostly through queries?

SQL autocomplete sounds simple until the query stops being simple. For simple SELECTs, almost any SQL autocomplete tool feels fine. Table name, column name, done.

The real test starts with messy and complex queries. Nested CTEs, aliases that made sense three years ago, subqueries, temp tables, joins across half the schema, and one column name that exists in five places.

That’s where basic suggestions are not enough. Good SQL IntelliSense should understand context. It should know which alias you’re inside, what columns are available there, and not suggest random objects from the whole database like it’s guessing in the dark.

We see this pain a lot regardless of the DBMS: SQL Server, MySQL, PostgreSQL, Oracle, etc. Autocomplete is useful only when it saves time without making you double-check every suggestion.

For us, the best autocomplete behavior is boring: correct syntax, correct names, correct context, fewer interruptions, and no fighting the editor. What usually breaks autocomplete for you?

SQL formatting feels like one of those things nobody cares about until they inherit a query from hell. A short query can look ugly and still be fine. But a huge report query with nested joins, random aliases, and conditions added by five different people over two years? That’s where formatting starts to matter. A SQL formatter won’t make bad SQL good. Would be nice, but no. It does make the mess easier to read. Same indentation, joins in predictable places, WHERE conditions not glued together like a ransom note. The only thing I hate is when a SQL beautifier goes too far and turns a normal query into a 200-line waterfall. Do you format SQL properly, or only clean it up when it gets embarrassing?