Use DataGrip query consoles, history, quick docs, inspections, and editor tools to run SQL faster while making fewer destructive mistakes.
Key takeaways
- Treat each query console as a workspace, because new consoles create new connection sessions by default.
- Switch to single session mode only when you need temporary tables or session state to survive across consoles.
- Use Query History and Local History before rewriting SQL you already ran or accidentally deleted.
- Preview table DDL, parameter behavior, and syntax fixes in the editor before executing a statement.
- Let inspections and the Productivity Guide show where your SQL habits can be cleaned up or accelerated.
Treat query consoles as separate workspaces
DataGrip query consoles work like disposable SQL workbenches. Because they are already attached to a data source, they let you start typing immediately without the setup friction that often turns small database checks into a context switch.
The main habit to build is separation. A console for ad hoc reads, another for a risky migration draft, and a third for performance checks is easier to reason about than one giant tab full of half-finished statements.