Skip to main content
Community Hub

Preflight checks for SAP ASE

TL;DR

Before running the SAP ASE crawler, run preflight checks to perform necessary technical validations.

Your AI can read this via Docs MCPInstall MCP →Connect

Before running the SAP ASE crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are completed:

Connectivity check​

Verifies that Atlan can connect to your SAP ASE server and checks the server version.

✅ Connected to SAP ASE server '$serverName'

❌ Connection failed: $error

If the server version is below 16.0, the check passes with a warning that user-defined functions (Function assets) aren't available.

Schemas check​

Verifies that the include and exclude filters match at least one schema across the in-scope databases.

✅ Found $schemaCount schemas across $databaseCount database(s) matching the filter

❌ The filter matched no schemas — nothing would be crawled

A SELECT permission denied (ASE error 229) failure means the Atlan user can't read the system catalogs in one of the in-scope databases - check the setup steps.

Tables check​

Counts the tables that match the include and exclude filters across the in-scope databases.

✅ Found $tableCount tables matching the filter

⚠️ Skipped — no schemas matched

See also​