# JDBC Connectors Your customers may want to ingest some of the data for their Aisera integration directly from a database. For instance, if your customer has a large amount of user data.\ \ Other example use cases include: * Spinning up a **MySQL database** on Railway for integration testing * Testing a **PostgreSQL query** using Neon with sample data * Evaluating schema design in a **MariaDB** instance without local setup Choose JDBC options to integrate a database directly to your Aisera Gen AI platform. The JDBC Connectors can connect via any JDBC driver to a database and then ingest data to your Aisera Gen AI platform.

The Aisera Gen AI platform supports the following JDBC connections: * Amazon Redshift * Snowflake * Trino * MySQL * MariaDB * PostgreSQL Like all Aisera connectors, you need to first create an Integration between the JDBC connector and your Aisera Gen AI platform Tenant and then create a Data Source using that Integration. A JDBC Connector can ingest data which correspond to the supported Aisera Entities, such as: * Users * Articles * Tickets It is a best practice to create an Aisera Service User to connect to your data source. This user needs Read permission and login credentials for the database.\ \ After you’ve created the connection for your Tenant, you can create an application/bot to associate with this Data Source. ## Setup Integration Parameters The following screenshots describe how to set up some of these JDBC connections. ### Snowflake Integration In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db) * URL (example: `a801.east-us-6.azure.mysnowflake.com` )

### Redshift Integration In Configuration Tab : * Endpoint (example: `localhost:5439/your_db`) In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db)

### Trino Integration In Configuration Tab : * Endpoint host:port/catalog/schema (example: `localhost:443/catalog/myschema`) In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db)

### MySQL Integration In Configuration Tab : * Endpoint host:port In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db)

### MariaDB Integration In Configuration Tab : * Endpoint host:port In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db)

### PostgreSQL Integration In Configuration Tab : * Endpoint host:port In Authentication Tab : * Username (user to connect to db - needs read access) * Password (password to connect to db)

## Setup the Data Source 1. Click **+ New Data Source**. 2. Select **JDBC**. 3. Create a **Name**, Select data source **Functions** (such as, for ingesting Users > LearnUsers) and choose a **Schedule.**

5. Change to the **Configuration** tab. 6. Type the **SQL Query** and Select the **Integration**. * **SNOWFLAKE EXAMPLE**\ `database.schema.table` (you need to replace in the query) * database * schema * table

* **REDSHIFT EXAMPLE**

* **TRINO EXAMPLE**

* **MYSQL EXAMPLE**

* **POSTGRESQL EXAMPLE**

Use the Limit field to paginate the requests that you send to the database. For instance, set the limit to 500 if you want to retrieve the first 500 users and then the next 500 users. If you have set a Limit value, then you should not also include a Limit clause in the SQL Query. Use the **Start Date** and **End Date** fields to define a range, such as: `select * from students where ADMISSION_DATE between {_startDate_} and {_endDate_}` Only use the **Database** field if the SQL Query calls a table from a different database than the one you have defined in the integration. ## Mapping Fields You need to manually define the mappings for each data source based on the columns from the table with the data you want to ingest, and the Aisera entity you want to map to each column. ### Examples