Skip to main content
PawSQL Client brings SQL review and optimization into the tools developers already use. Depending on the integration, PawSQL can review a statement before DBeaver executes it or return rewrites, index recommendations, and validation evidence from a code editor.

​
Available integrations

Earlier documentation and some commands use the name PawSQL Advisor for the JetBrains plugin. This guide uses PawSQL Client for JetBrains for the product family and retains legacy command names where they appear in the interface.

​
Choose an integration

​
How the integrations differ

​
How integrations connect to PawSQL

These integrations connect to PawSQL Cloud or PawSQL Server and operate within the projects and workspaces available to the authenticated user. Installation, endpoint configuration, and commands are documented separately for each platform. Before you begin, obtain the PawSQL endpoint, an authorized account, and a workspace that represents the target database. See Authentication and Workspaces and Database Context for shared concepts.

​
In this section

DBeaver integration

Configure pre-execution review, severity thresholds, and datasource exclusions.

JetBrains integration

Optimize selected SQL, files, folders, and MyBatis Mapper input.

Visual Studio Code integration

Tune the current statement in source code or a SQL file.

PawSQL MCP

Optimize SQL through natural language in an MCP-compatible coding assistant.

​
Shared security boundaries

  • Install packages only from a trusted PawSQL release channel and verify the publisher and version.
  • Keep credentials in the client’s secure storage and out of source control.
  • Match the workspace to the SQL target and deployment environment.
  • Exclude a DBeaver datasource only when bypassing pre-execution review is intentional.
  • Treat rewritten SQL and index DDL as candidates that require engineering validation.
  • Assess resource and locking impact before enabling live execution or What-If validation against production.
An extension does not replace database authorization, change approval, backups, or rollback controls. Use PawSQL results as technical evidence within those processes.

​
Next step

Install the extension first (see Install IDE Extensions), then open the guide for your client and complete its configuration. For the first check, use a sanitized, read-only statement with a predictable result to verify the endpoint, permissions, and workspace.