Skip to main content
A connected workspace retrieves metadata from the target database through a dedicated account. This approach is designed for recurring team use, evolving schemas, production query governance, and features that depend on plans or runtime information.

Goal

Connect PawSQL to a database and synchronize the authorized schemas, tables, columns, constraints, and indexes into a workspace.

Prerequisites

A connected workspace requires:
  • Network reachability from the PawSQL service to the database;
  • a database and version supported by the PawSQL release;
  • a dedicated database account;
  • an approved database or schema scope;
  • known TLS, allowlist, proxy, and connection-limit requirements;
  • permission to create both workspaces and connections.

Apply least privilege

Do not use a database administrator account or reuse an application account. A failed metadata read is not a reason to grant unrestricted privileges.

Connection inputs

Typical inputs include connection name, engine and version, host, port, database or service identifier, username, secret, TLS configuration, optional driver properties, and schema scope. Exact fields vary by database and PawSQL release.

Create the workspace

With the database connection as the source, create the workspace in these steps:
1

Create a workspace

Open workspace management in the correct organization or project, then enter a name and purpose.
2

Select engine and version

Match the real database deployment.
3

Choose database connection

Create a connection or select an approved shared connection.
4

Enter connectivity settings

Provide endpoint, identity, and security parameters.
5

Test the connection

Validate network, TLS, authentication, and basic catalog access.
6

Limit synchronization scope

Select only the databases or schemas required by the project.
7

Synchronize and review

Inspect created, updated, skipped, and failed objects.

Scope guidance

A focused schema scope reduces synchronization time, limits metadata exposure, and makes object selection easier. Include multiple schemas only when the target SQL genuinely crosses those boundaries.

Expected Result

After synchronization completes, the workspace contains the authorized schemas, tables, columns, constraints, and indexes, ready for SQL review and optimization.

Verification

Confirm the workspace was created correctly by checking that the target schema is visible, tables, columns, and indexes can be read, the database version is recognized, and metadata synchronization completed without widespread failures.

Troubleshooting

Next steps

Verify connectivity