## Crawl SAP HANA

URL: https://docs.atlan.com/apps/connectors/database/sap-hana/how-tos/crawl-sap-hana

> Extract metadata from SAP HANA to catalog databases, schemas, tables, views, and columns. Discover and govern your enterprise data assets after configuring user permissions.

Extract metadata from your [SAP HANA](https://docs.atlan.com/llms/connectors/sap-hana/set-up-sap-hana/llms.txt) instance into Atlan to catalog databases, schemas, tables, views, and enable data discovery. After configuring the necessary user permissions, you can establish a connection and crawl your SAP HANA environment to extract lineage and column-level details.

## Prerequisites

Before you begin, make sure you have:

* Configured [SAP HANA user permissions](https://docs.atlan.com/llms/connectors/sap-hana/set-up-sap-hana/llms.txt) with metadata read access
* SAP HANA database connection details (host, port, credentials)
* Reviewed the [order of operations](https://docs.atlan.com/llms/catalog/connector-capabilities/order-workflows/llms.txt) for workflow execution

## Create crawler workflow

Create a new SAP HANA crawler workflow in Atlan by selecting the SAP HANA connector package, configuring your extraction method and connection details, and running the crawler to extract metadata.

1. In your Atlan workspace, click **Connectors** in the left sidebar.
 * If you are using the **Old UI (Classic)**, click **New Workflow** in the top navigation.

2. Click **Marketplace**.

3. Search for **SAP HANA Assets** and select it.

4. Click **Install**.

5. Once installation completes, click **Setup Workflow** on the same tile.

### Configure extraction

Select your extraction method and provide the connection details.

:::warning Offline extraction sunset
The offline extraction method has been sunset and is no longer available. For on-premises or network-restricted environments, use the **Agent** extraction method with [Self-Deployed Runtime](https://docs.atlan.com/llms/platform/self-deployed-runtime/llms.txt).
:::

### Direct

In **Direct** extraction, Atlan connects to your database and crawls metadata directly.

 1. For _Host_, enter the host name for your SAP HANA instance.
 2. For _Port_, enter the port number for your SAP HANA instance.
 3. For _Username_, enter the username you created for the instance.
 4. For _Password_, enter the password for the username.
 5. Click the **Test Authentication** button to confirm connectivity to SAP HANA.
 6. Once authentication is successful, navigate to the bottom of the screen and then click **Next**.

### Agent

In **Agent** extraction, Self-Deployed Runtime executes metadata extraction within your organization's environment.

1. Install Self-Deployed Runtime if you haven't already:
 - [Install via Docker Compose](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-docker-compose/llms.txt)
 - [Install on Kubernetes](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-kubernetes/llms.txt)
2. Select the **Agent** tab.

3. Store sensitive information in the secret store configured with the Self-Deployed Runtime and reference the secrets in the corresponding fields. For more information, see [Configure secrets for workflow execution](https://docs.atlan.com/llms/platform/secure-agent/configure-secure-agent-for-workflow-execution/llms.txt).

4. For details on individual fields, refer to the Direct extraction tab.

5. Click **Next** after completing the configuration.

### Configure connection

Set up connection details including a descriptive name, admin access, and data access permissions.

1. Provide a _Connection Name_ that represents your source environment. For example, you might use values like `production`, `development`, `gold`, or `analytics`.

2. To change the users able to manage this connection, update the users or groups listed under _Connection Admins_. If you don't specify any user or group, nobody can manage the connection, including admins.

3. To prevent users from querying SAP HANA data, change _Allow SQL Query_ to **No**. This option applies only to Direct extraction.

4. To prevent users from previewing SAP HANA data, change _Allow Data Preview_ to **No**. This option applies only to Direct extraction.

5. Click **Next** at the bottom of the screen.

### Configure crawler

Configure crawler settings to control which assets to include or exclude. If an asset appears in both filters, the exclude filter takes precedence.

1. To select specific assets for crawling, click **Include Metadata**. By default, all assets are included.

2. To exclude specific assets from crawling, click **Exclude Metadata**. By default, no assets are excluded.

### Run crawler

Run preflight checks to validate your configuration, then execute the crawler immediately or schedule it to run on a recurring basis.

1. To verify [permissions and configuration](https://docs.atlan.com/llms/connectors/sap-hana/preflight-checks-for-sap-hana/llms.txt) before running, click **Preflight checks**.

2. Choose your run option:
 - To run the crawler once immediately, click **Run** at the bottom of the screen.
 - To schedule the crawler to run hourly, daily, weekly, or monthly, click **Schedule Run** at the bottom of the screen.

Once the crawler completes, you can view the assets in Atlan's asset page.

## See also

* [What does Atlan crawl from SAP HANA](https://docs.atlan.com/llms/connectors/sap-hana/what-does-atlan-crawl-from-sap-hana/llms.txt): Complete reference of assets and metadata discovered during crawling
* [Preflight checks for SAP HANA](https://docs.atlan.com/llms/connectors/sap-hana/preflight-checks-for-sap-hana/llms.txt): Validation checks for permissions and configuration before running the crawler

---