## Set up SAP ASE

URL: https://docs.atlan.com/apps/connectors/database/sap-ase/how-tos/set-up-sap-ase

> Create a least-privilege SAP ASE login and grant the catalog access Atlan needs to crawl metadata.

:::warning Who can do this?
You probably need your SAP ASE administrator to run these commands - you may not have access yourself.
:::

Atlan supports basic username and password authentication for fetching metadata from SAP ASE (Adaptive Server Enterprise, formerly Sybase ASE). Atlan only runs read-only `SELECT` queries on system catalogs - it never reads or modifies the data in your tables.

## Prerequisites

Before you begin, make sure you have:

* SAP ASE version 15.0 or later. Version 16.0 or later is required to crawl user-defined functions - on earlier versions, function extraction is skipped.
* Administrator access to create a login and add it as a user to the databases you want to crawl.

## Create login

Create a dedicated login for Atlan:

```sql
sp_addlogin atlan_user, '<password>'
```

* Replace `<password>` with a strong password for the login.

## Add user to each database

Add the login as a user in every database you want to crawl:

```sql
use <database>
go
sp_adduser atlan_user
go
```

* Replace `<database>` with the name of each database you want to crawl. Databases where the login isn't a user can't be crawled.

## Verify catalog access

Atlan reads the following system catalogs with `SELECT` queries:

* `master..sysdatabases` and `master..syslogins` - to list databases and resolve their owners
* `sysusers`, `sysobjects`, `syscolumns`, `systypes`, `syskeys`, and `syscomments` in each crawled database - to extract schemas, tables, views, columns, stored procedures, and functions

In most SAP ASE installations, database users can read system catalogs by default. If your security configuration restricts catalog access, grant `SELECT` on these tables to the Atlan user in each database.

## Prepare SSL truststore

If your SAP ASE server requires SSL/TLS connections, prepare a JKS or PKCS12 truststore containing the certificate authority (CA) certificate that signed your server's SSL certificate:

```bash
keytool -import -alias sap-ase -file <ca-certificate>.pem -keystore truststore.jks
```

* Replace `<ca-certificate>` with the path to your CA certificate file.

You provide this truststore when [configuring the crawler](https://docs.atlan.com/llms/connectors/sap-ase/crawl-sap-ase/llms.txt).

## Next steps

[Crawl SAP ASE assets](https://docs.atlan.com/llms/connectors/sap-ase/crawl-sap-ase/llms.txt): Configure and run the crawler to extract metadata from SAP ASE

---