Skip to main content

Configure a database

To bring your own data into Tellery, You can set up your database profile on Settings > Databases.

A database profile, which is the necessary configurations we have to made to connect to your data warehouse, consists of:

  • Name (the unique identifier of your profile)

  • Connector type (what kind of database you are connecting)

  • Configurations & Optionals (host, port, etc. differs from each kind of connector. For more details, see sections below)

Snowflake#

To connect with Snowflake, you need to provide:

FieldDescriptionExampleRequired
Account NameYour Snowflake account namexy12345yes
Region IdYour Snowflake region Idus-ease-2.awsyes
UsernameYour Snowflake usernamelogin_nameyes
PasswordYour Snowflake passwordyour_passwordyes
RoleThe default access control role to use in the Snowflake sessionSYSADMINno
WarehouseThe virtual warehouse to run queriesCOMPUTE_WHno

Snowflake connector supports importing data from csv without any other configuration.

Redshift#

To connect with Redshift, you need to provide:

FieldDescriptionExampleRequired
EndpointThe hostname of your Redshift clusterexamplecluster.abc123xyz789.us-west-2.redshift.amazonaws.comyes
PortThe port number that you specified when launched, usually 54395439yes
UsernameThe username you created when initializing clusteryour_usernameyes
PasswordThe password your created when initializing clusteryour_passwordyes
DatabaseThe logical database to connect to and run queries againstmy_dbyes*
note

Since the Redshift is based on PostgreSQL, the configuration of Redshift will be similar to that of PostgreSQL. If you are interested in this topic, please read the note in PostgreSQL

Optionals#

To support importing csv to Redshift, you need to provide aws credentials for uploading csv file into your S3. Note that the region of S3 must be the same as your Redshift cluster.

PostgreSQL#

FieldDescriptionExampleRequired
EndpointThe hostname of your PostgreSQL databaselocalhostyes
PortThe port number that you specified when launched, usually 54325432yes
UsernameThe user / role that granted access to your databaseyour_usernameyes
PasswordYour passwordyour_passwordyes
DatabaseThe logical database to connect to and run queries againstmy_dbyes*
note

The database argument is mandatory for postgreSQL, by default it would be the same as your username.

In the setting of postgreSQL, databases stand for the topmost hierarchical level of organizing database objects, so you cannot do cross-database queries without other plugins.

Therefore, our connector will restrict your accessibility into the database you configured, all of the other databases are invisible even if you got the permission.

This setting will be also applied to Redshift.

BigQuery#

The only thing you need to connect your BigQuery is your key file, which can be generated following the instruction here

The uploaded json file should populate the following fields:

  • Project id
  • Private key id
  • Private key
  • Client email
  • Client id
  • Auth uri
  • Token uri
  • Auth provider x509 cert url
  • Client x509 cert url