# Databases/Warehouses

Some of the databases and warehouse available when clicking on *Add New Connection* might require more information than the one shown in the previous section, or could have extra options.

## Redshift

To add a Redshift connection, you will have to provide:

* Connection name, which you will assign to this connection for internal use.
* A JDBC URL. A sample JDBC URL is shown under this text.

> jdbc:redshift://redshift-cluster-1.XXXXXXXXXX.us-east-1.redshift.amazonaws.com:5439/dev?ssl=false

* Credentials, which will be a username and a password that will provide access to this database.

Optionally, you may provide *s3TempDir* and *s3AwsIamRole* for better performance, as explained in the following link.

{% embed url="<https://awsdba.cloud/2019/05/10/redshift-iam-role-for-copy-unload-to-s3/>" %}

> **s3TempDir**
>
> s3n://**\<S3\_Bucket>**/
>
> **s3AwsIamRole**
>
> arn:aws:iam::**XYZ**:role/Redshift\_Role

<figure><img src="https://2027008842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaO8uOTM2rdJeIbVeXK0c%2Fuploads%2FXfCDRY7ujiacxT55S3qd%2Fimage.png?alt=media&#x26;token=0a5df49a-9935-4937-aacb-fe34e3f87952" alt=""><figcaption><p>Redshift Configuration</p></figcaption></figure>

It is recommended to create a read only user account in Redshift. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. svv\_table\_info
2. information\_schema.views

## SQL Server

To add an SQL Server connection, you will have to provide:

* Connection name, which you will assign to this connection for internal use.
* A JDBC URL. A sample JDBC URL is shown under this text.

> jdbc:sqlserver://XXXXXX:1433;databaseName=XXXXXXX;

* Credentials, which will be a username and a password that will provide access to this database.

<figure><img src="https://2027008842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaO8uOTM2rdJeIbVeXK0c%2Fuploads%2FxAco9gtsF3kYqqyOFiWf%2FScreenshot%202024-12-16%20135351.png?alt=media&#x26;token=5b687ec4-6209-4174-80d1-6a26b5118b13" alt=""><figcaption><p>SQL Server Configuration</p></figcaption></figure>

It is recommended to create a read only user in Sql Server. The read only user id should have read only access on the databases/schemas where data resides and also have access to the following system tables to read the metadata of all the tables.

1. sys.objects
2. sys.columns
3. sys.types
4. sys.indexes
5. sys.index\_columns
6. sys.columns
7. sys.key\_constraints
8. sys.tables
9. sys.all\_columns

## Postgres

To add a PostgresSQL connection, you will have to provide:

* Connection name, which you will assign to this connection for internal use.
* A JDBC URL. A sample JDBC URL is shown under this text.

> jdbc:postgresql://\<jdbcHost>:XXXX/\<jdbcDatabaseName>

* Credentials, which will be a username and a password that will provide access to this database.

If SSL is enabled, additional parameters will be required for the JDBC URL as shown under this text.

> jdbc:postgresql://\<jdbcHost>:XXXX/\<jdbcDatabaseName>\&ssl=true\*\*\&sslmode=require\&sslfactory=org.postgresql.ssl.NonValidatingFactory\*\*

<figure><img src="https://2027008842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaO8uOTM2rdJeIbVeXK0c%2Fuploads%2FFK9b1TM7GITyCVRUEVXz%2Fimage.png?alt=media&#x26;token=38506fd7-7882-493d-add2-ce1ba2dc43bc" alt=""><figcaption><p>Postgres configuration</p></figcaption></figure>

#### Create a new read only user for Postgres Testing

The user id should only have read permission on the data. Also, Vexdata needs permission to read metadata. The user id should have read only permissions on the following system tables

```
pg_class
information_schema.table_constraints
information_schema.columns
pg_namespace
pg_catalog
```

## Snowflake

To add a Snowflake connection, you will have to provide:

* Connection name, which you will assign to this connection for internal use.
* A JDBC URL. A sample JDBC URL is shown under this text.

> jdbc:snowflake://XXX72530.us-east-1.snowflakecomputing.com/?db=\<jdbcDatabaseName>\&schema=\<schemaName>

* Credentials, which will be a username and a password that will provide access to this database.

<figure><img src="https://2027008842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaO8uOTM2rdJeIbVeXK0c%2Fuploads%2F8kmE9XCsKJbTn5JKRQkg%2Fimage.png?alt=media&#x26;token=ec6044c4-6ef2-4f7c-92e0-7cbf6258b177" alt=""><figcaption><p>Snowflake Configuraiotn</p></figcaption></figure>

It is recommended to create a read only user account in Snowflake. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. information\_schema.columns
2. information\_schema.tables

## Oracle <a href="#snowflake" id="snowflake"></a>

It is recommended to create a read only user account in Oracle. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. sys.dba\_tables
2. sys.dba\_constraints
3. sys.dba\_cons\_columns
4. sys.all\_users
5. all\_ind\_columns
6. all\_indexes
7. all\_cons\_columns
8. all\_constraints

**To grant read only permission to catalog tables**

\
[`grant SELECT_CATALOG_ROLE to <user>;`](#user-content-fn-1)[^1]

## **Maria**​

It is recommended to create a read only user account in Maria. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. information\_schema.tables
2. information\_schema.columns
3. information\_schema.table\_constraints
4. information\_schema.key\_column\_usage
5. information\_schema.referential\_constraints
6. information\_schema.statistics

## DB2

It is recommended to create a read only user account in DB2. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. syscat.tables
2. syscat.columns
3. sysibmadm.admintabinfo
4. syscat.tabconst
5. syscat.keycoluse

## Bigquery

It is recommended to create a read only user account in Maria. The user id needs to have access to the following system tables to read the metadata of all the tables.

1. INFORMATION\_SCHEMA.SCHEMATA
2. INFORMATION\_SCHEMA.TABLES
3. INFORMATION\_SCHEMA.COLUMNS

[^1]:


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vexdata.io/getting-started/settings/untitled/redshift.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.