> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pawsql.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> PawSQL 是一个产品：Cloud 是公网部署形态，Engine / Optimizer / Auditor / Advisor / Patroller 是同一产品的组件与交付形态，不是彼此独立的产品。 / PawSQL is a single product: Cloud is the public deployment form, while Engine / Optimizer / Auditor / Advisor / Patroller are components and delivery forms of the same product, not separate products.
> 术语以站内术语表为准：SQL 审核对应英文 SQL Review，查询重写对应 Query Rewrite，索引推荐对应 Index Recommendation；英文内容统一用 Review，不用 Audit。 / Use the site glossary for terminology: 审核 is SQL Review, 重写 is Query Rewrite, 索引推荐 is Index Recommendation; English content uses Review, never Audit.
> 引用能力范围或版本支持时以对应页面为准；标注 unknown、或 status 非 published 的内容表示尚未经产品核实，不应作为事实引用。 / Cite capability scope and version support from the corresponding page; content marked unknown, or with a status other than published, is not yet product-verified and must not be cited as fact.

# Verify Installation and Connectivity

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

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.

```mermaid theme={null}
flowchart TD
    A["Service reachable"] --> B["Authentication succeeds"]
    B --> C["Permissions are correct"]
    C --> D["Workspace is usable"]
    D --> E["SQL task completes"]
```

## 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.

<Tip>
  Successful sign-in with missing resources is usually an authorization issue. A complete sign-in failure points to authentication or connectivity.
</Tip>

## 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

<Steps>
  <Step title="Select a non-production workspace">Verify engine, version, and schema.</Step>
  <Step title="Submit a sanitized query">Use a complete read-only statement.</Step>
  <Step title="Wait for completion">Confirm normal queued, running, and completed states.</Step>
  <Step title="Inspect the result">Verify parsing, object resolution, and result details.</Step>
  <Step title="Record acceptance evidence">Capture version, workspace, task ID, date, and outcome.</Step>
</Steps>

## Client-specific checks

<Tabs>
  <Tab title="IDE">
    * Extension enabled and compatible
    * Connection test successful
    * Project and workspace selectable
    * Selected SQL returns results
  </Tab>

  <Tab title="MCP">
    * MCP process starts
    * PawSQL tools are discoverable
    * The correct service identity is used
    * A sanitized tool call succeeds
  </Tab>

  <Tab title="API">
    * Authentication succeeds
    * A test task can be created
    * Task status and results can be retrieved
    * Errors do not expose secrets
  </Tab>
</Tabs>

## Diagnostic map

| Symptom                   | Investigate first                                      |
| ------------------------- | ------------------------------------------------------ |
| Page unavailable          | Service, URL, DNS, proxy, firewall, TLS                |
| Sign-in failure           | Account, identity provider, system time, environment   |
| No menus                  | Role, project, entitlement, feature enablement         |
| Client connection failure | Endpoint, token, proxy, certificate trust              |
| No workspace              | Membership, permissions, project scope                 |
| Parsing failure           | Dialect, version, statement completeness, placeholders |
| Objects unresolved        | Schema, DDL, metadata refresh, identifier case         |
| Task remains queued       | Analysis service, queue, concurrency, resources        |

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

## 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

<CardGroup cols={2}>
  <Card title="Create a workspace" href="/en/user-guide/workspaces/index" />

  <Card title="One-minute SQL optimization" href="/en/getting-started/quickstart" />
</CardGroup>