What's New in DataGrip 2026.1

We have redesigned the flow for working with query files side by side with query consoles. You can now use either just files or just consoles, or both at the same time, depending on your tasks and workflow.

To create a new query file, right-click a data source and select New | Query File or press Shift+Cmd+J (macOS) or Ctrl+Alt+Shift+Q (Windows/Linux). Then, in the New Query File dialog, specify the file's name and the directory where you want to store it. To store it within the current project and associate the file with it, specify the current project directory or one of its subdirectories.

You can now access your query files in the database explorer. We have added a Query Files folder, which appears under each data source node. To toggle this folder's visibility, click View Options on the tool window toolbar, and then select or deselect the Query Files option.

Different tasks require different information to be visible. We've added some settings to ensure that the presentation of query files gives you the right info for your specific use case. You can use these settings to toggle whether data source names are displayed, apply schema colors, and use the icon of the attached data source with your query files.

We have implemented a way to store data source settings as a template in your JetBrains Account. When stored this way, the template is available in every JetBrains IDE with database functionality provided through your JetBrains Account. These templates store settings from the General and Advanced tabs of the Data Source and Drivers dialog, but exclude your database credentials.

You can create a template in the Data Source and Drivers dialog. On the Data Sources tab, select the data source you want to create a template from and click Save as template.

The new template will appear on the Data Source Templates tab. You can create a new data source that uses the template at any time with the Create Data Source button.

1. The Data Sources, Clouds, Drivers, and DDL Mappings sections are now the main tabs in the dialog, located on the left-hand side.
2. If the Comment field is empty, it is hidden by default. To display it, click Add Comment next to the Name field.
3. If the driver selected in the Driver dropdown menu has yet to be downloaded, a Download option appears next to the menu. Click this to download the driver.
4. The Connection type dropdown options are now tabs. If a data source has more than three connection types, they are displayed as a dropdown.

In addition, the Create DDL Mapping action has been removed. You can create a DDL mapping on the DDL Mappings main tab.

We have made a few updates to the Explain Plan workflow to make it more discoverable, informative, and easy to use:

• The list of options in the Explain Plan dropdown on the code editor toolbar has been shortened to just two: Explain Plan and Explain Analyse.

• In the Services tool window, the Query Plan tab that displays the plan has been moved to the same level as the Output and Result tabs. It also has a new icon.

• In the Query Plan tab, you can now view the details of each plan row in a separate panel on the right-hand side of the tab.

• For the cells that contain a table name, quick documentation is available in a popup when you hover the cursor over the table.

• The different views available for a query plan are displayed in separate sub-tabs. These inner tabs can be seen at the bottom of the Query Plan tab. They are hidden by default and appear only when more than one tab is open. To open the Total Cost or Startup Cost tab, click Flame Graph on the left-hand toolbar and select the view you need.

You can now copy a query plan in the database's native format, for example, JSON or XML. To do this, click the Copy Original Query Plan button at the top of the left toolbar. This is supported for PostgreSQL, Amazon Redshift, MySQL, MariaDB, Oracle, Microsoft SQL Server, and Snowflake.

We have made the Suppress for back label references option easier to find and use. Previously, it was only available in the Settings dialog under Editor | Inspections | SQL.

Now, it can be toggled in intention actions. To enable or disable it, open the list of intention actions by pressing Alt+Enter (Windows/Linux) or Option+Enter (macOS), navigate to Enable option "Suppress for back label references", and select or deselect the Suppress for back label references checkbox.

We have added the Execute Selection as Single Statement action to the context menu of a code selection. Use this when you need to execute a certain chunk of code and DataGrip isn't parsing it properly.

The code editor caret has received two new options for the movement animation to improve your typing experience.

We realize that animation preferences vary quite a lot. With this in mind, we carefully developed our own mode of caret movement: Snappy. It ensures smooth animation without making the caret feel slow and unresponsive or overloading the interface with excessive action. In this mode, the caret initially jumps quickly to its new position, but then slows down a bit and "settles into" position. The result feels quick yet smooth.

In the other caret animation mode, Gliding, the caret moves smoothly, making jumps easy to follow with your eyes. This mode is similar to the ones you see in other popular text editors.

To try these new animation modes, open the Settings dialog, navigate to Settings | Editor | General | Appearance, enable the Use smooth caret movement option, and select the mode you want to use.

DataGrip now supports creating and modifying JSON indexes for Microsoft SQL Server. You can work with them in code generation and also use the indexes in the Create and Modify dialogs.

For better discoverability, we have moved the Show Geo Viewer button to the data editor toolbar.

Previously, when Delete actions were invoked, DataGrip deleted files permanently instead of moving them to the bin. We've added a setting that sends files to the bin instead. It's called Move files to the bin instead of deleting permanently, and it is enabled by default.

You can change this setting in Settings | Appearance & Behavior | System Settings.