Why JetBrains Rolled Back DataGrip’s Query Console in 2025.3 and How to Adapt

One week after releasing DataGrip and the IntelliJ IDE series 2025.3, JetBrains announced a rare decision to roll back the major changes to the SQL query workflow, returning the Query Console to its default behavior. The rollback will be delivered in the 2025.3.1 maintenance release and applies to DataGrip as well as the Database Tools plugin in all JetBrains IDEs.

In version 2025.3 the core SQL workflow was refactored: the new Query File replaced the existing Query Console , the file model was unified to make queries behave more like files, and the change was internally dubbed “A Farewell to Consoles”.

User feedback was swift and concentrated. The redesign caused several critical issues, especially:

Confusion when using Global Data Sources.

Disruption of established query habits.

Reduced usability in multi‑IDE or multi‑project workflows.

After evaluating the impact, the team concluded that continuing to patch the redesign would create more problems, so they chose a full rollback to avoid further user pain.

“Continuing to patch is worse than rolling back entirely; we want to prevent more users from falling into traps.”

The official announcement emphasized that, rather than incremental fixes, the priority is to restore the stable behavior as quickly as possible.

What the 2025.3.1 rollback does:

Query Console becomes the default workflow again.

Behavior is identical to versions prior to 2025.3.

This is a complete rollback, not a compromise solution.

Impact on users:

If you have not upgraded to 2025.3, there is no effect; your workflow remains unchanged.

If you have already upgraded, it is strongly recommended to upgrade to 2025.3.1 promptly to shorten the period of abnormal behavior.

How to handle existing Query Files created during the migration period:

Option 1: Delete unnecessary Query Files

In DataGrip: use the Files tool window and remove the /queries directory.

In other IDEs: delete the /.idea/queries directory from the Project tool window.

Option 2: Convert to Query Console (recommended) Move the Query File under the appropriate data source; after conversion you regain the familiar console experience. Scratches and Consoles | Database Consoles Option 3: Keep temporarily JetBrains plans to bring back an improved Query File workflow early next year, coexisting with Query Console rather than replacing it.

The team reiterated their commitment to a “zero‑regression” standard, acknowledging that this release did not meet that goal and taking full responsibility for the misstep.

“We made a mistake; our top priority now is to restore your workflow as quickly as possible.”