Skip to main content
PawSQL IDE extensions bring SQL review and optimization into the editor. Each extension connects to PawSQL Cloud or PawSQL Server and operates within the projects and workspaces available to the authenticated user.

Goal

Learn how to install the PawSQL extension for DBeaver, JetBrains IDEs, or Visual Studio Code and connect it to a PawSQL service.

Before you install

  • A supported DBeaver, JetBrains IDE, or Visual Studio Code version;
  • the PawSQL Cloud or PawSQL Server endpoint;
  • a client credential where required;
  • access to the intended project and workspace;
  • marketplace connectivity or an approved offline package.

Install the extension

DBeaver installs extensions from a software repository rather than a marketplace. Available sources:
  • the official repository https://www.pawsql.com/repository; and
  • the Eclipse Marketplace page for PawSQL.
1

Open the install wizard

Choose Help > Install New Software in DBeaver.
2

Add the PawSQL repository

Enter the repository URL https://www.pawsql.com/repository in Work with and click Add.
3

Select and install

Select PawSQL for DBeaver and complete the wizard.
4

Restart DBeaver

Save open work and restart the client when prompted.
After installation, confirm that PawSQL Client settings appear under Preferences. See Review SQL Before Execution in DBeaver for pre-execution review and threshold configuration.

Offline installation

When the IDE cannot reach the marketplace, use an offline package supplied by your administrator. Before installing, confirm:
  • the package comes from PawSQL or an approved internal software repository;
  • the version is compatible with both the IDE and the PawSQL service version;
  • the package has passed your organization’s security review;
  • the upgrade and rollback path is defined.
The offline installation entry point varies by IDE version; use the plugin-management page for that IDE.

Connect the extension

1

Open PawSQL settings

Use the IDE settings or the PawSQL tool window.
2

Enter the endpoint

Add the complete Cloud or Server URL and label test and production endpoints clearly.
3

Add credentials

Use the client’s secure credential facility where available. Do not store tokens in project files.
4

Test the connection

Verify network access, TLS trust, authentication, and service health.
5

Select context

Choose the organization, project, and workspace, then verify the database engine and schema.

Validate the extension

  1. Open a file containing a complete SQL statement.
  2. Select a sanitized read-only query.
  3. Run a PawSQL analysis command.
  4. Confirm that a task is created and results return.
  5. Verify database dialect and object resolution.
If connectivity works but recommendations are unexpected, inspect the selected workspace before reinstalling the extension.

Security guidance

  • Never commit a token to source control.
  • Use the IDE or operating system credential store.
  • Separate production and non-production workspaces.
  • Review generated changes before applying them to source code.
  • Revoke credentials when a device or extension is no longer used.

Troubleshooting

Expected Result

After installation and connection, the extension appears in the IDE, and a PawSQL analysis command can create a task and return results.

Next steps

Authentication

Verify the installation

Developer tools

Workspaces