Skip to main content
A successful page load is not a complete installation test. Validate the chain in order: service, identity, permissions, workspace context, and SQL task processing.

​
Goal

Validate service reachability, authentication, authorization, workspace access, and SQL analysis as one end-to-end path.

​
Prerequisites

  • A deployed PawSQL service (Cloud or Server).
  • A non-production workspace and a sanitized, read-only test query.

​
Steps

Validate the chain in order: service access, authentication, authorization, workspace context, and SQL task processing.

​
1. Service access

  • The expected URL opens.
  • TLS is trusted and the hostname matches.
  • No proxy, gateway, or browser error appears.
  • IDE and MCP hosts can reach the same endpoint.
  • PawSQL Server operators confirm that required services are healthy.

​
2. Authentication

  • A web user can sign in.
  • The displayed account is correct.
  • Client credentials are active and unexpired.
  • Authentication errors do not disclose credentials in logs.

​
3. Authorization

  • The intended organization and project are visible.
  • Menus match the test user’s role.
  • The user can view or create a test workspace.
  • The user can create an SQL optimization task.
  • Restricted administrative features remain unavailable to standard users.
Successful sign-in with missing resources is usually an authorization issue. A complete sign-in failure points to authentication or connectivity.

​
4. Workspace context

  • Database engine and version are correct.
  • DDL import or database connection testing succeeds.
  • Required schemas, tables, and columns are visible.
  • Index metadata is present where required.
  • The test account can use the workspace.

​
5. SQL analysis

1

Select a non-production workspace

Verify engine, version, and schema.
2

Submit a sanitized query

Use a complete read-only statement.
3

Wait for completion

Confirm normal queued, running, and completed states.
4

Inspect the result

Verify parsing, object resolution, and result details.
5

Record acceptance evidence

Capture version, workspace, task ID, date, and outcome.

​
Client-specific checks

  • Extension enabled and compatible
  • Connection test successful
  • Project and workspace selectable
  • Selected SQL returns results

​
Diagnostic map

Acceptance records must not include passwords, complete tokens, connection strings, or unsanitized production SQL.

​
Expected Result

The service is reachable, sign-in succeeds, permissions are correct, the workspace is usable, and a SQL analysis task completes.

​
Verification

Complete each checklist item in the numbered order and record version, workspace, task ID, date, and outcome as acceptance evidence.

​
Next steps

Create a workspace

One-minute SQL optimization