---
title: "ODBC Connector"
slug: "odbc-connector"
description: "ODBC Data Access service provided by Sight Machine. With this service, you can seamlessly connect to the Sight Machine platform and access your data using your API Key and Secret. This documentation will guide you through the process of obtaining your credentials and connecting to the Sight Machine platform in various external products. "
updated: 2026-01-28T15:21:45Z
published: 2026-01-28T15:21:45Z
canonical: "docs.sightmachine.com/odbc-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sightmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ODBC Connector

# Introduction

Welcome to the ODBC Data Access service provided by Sight Machine. With this service, you can seamlessly connect to the Sight Machine platform and access your data using your API Key and Secret. This documentation guides you through the process of connecting to the Sight Machine platform in various external products.

If you have not obtained your API Key and Secret, please refer to the article, [Obtaining Your API Key and Secret](https://docs.sightmachine.com/docs/apis#obtaining-your-api-key-and-secret).

## Establishing a Connection

### Connecting with a Database Client

The Sight Machine database runs on PostgreSQL, so you need a database client with the appropriate drivers. Many clients use the JDBC driver, which you can find at [https://jdbc.postgresql.org](https://jdbc.postgresql.org). Refer to your software's documentation for specific driver requirements. Your data is stored in the *tenant_storage* database within the *sightmachine* schema.

To connect, use the following information as required by your software:

- **Host:** Your sightmachine.io domain
- **Port:** 5432
- **Database:** tenant_storage
- **Username:** Your API key
- **Password:** Your API secret

![](https://lh7-us.googleusercontent.com/N0pYgKpCu-cSiSOUwZre0TOjR8o_rmMIs9amTFZ-mrDiggMaAmXgNb160vvviXRhEbT0HeamJdMHefHZtucIrL2dsV0SVc2oz9-WNdtU7KczasAPPuZIEDfAwJMUrIK2viyDMZtVPBqLxiDzVvADg_I)

### Connecting with PowerBI

To retrieve data from the Sight Machine database using PowerBI, do the following:

1. In the main ribbon menu, click **Get Data**, and then click **More** at the bottom of the menu.
2. In the resulting dialog box with data options, click the **Database** category on the left.

![](https://cdn.us.document360.io/c65001f1-30e3-4f1d-b335-57abf64ebd31/Images/Documentation/image(2).png)
3. From the list on the right, click **PostgreSQL database**, and then click **Connect**.
4. On the next screen, type the server name. This should match your sightmachine.io domain from the website. The database to connect to is **tenant_storage**.

![](https://cdn.us.document360.io/c65001f1-30e3-4f1d-b335-57abf64ebd31/Images/Documentation/image.png)
5. Click either **Import** or **DirectQuery**, depending on your needs.
6. For your login credentials, type or paste your API key as the username and your API secret as the password.

![](https://cdn.us.document360.io/c65001f1-30e3-4f1d-b335-57abf64ebd31/Images/Documentation/image(4).png)
7. Click **Connect**. Once you are connected, you can easily select your data for direct import or apply custom transformations as required.

![](https://cdn.us.document360.io/c65001f1-30e3-4f1d-b335-57abf64ebd31/Images/Documentation/image(3).png)

You also have the option to view the native SQL query that is being executed, which can be helpful for debugging or gaining insights into your data.

![](https://lh7-us.googleusercontent.com/_gecf02OuT9t4NrVBaOTlk-p2JnvMd9s5mriaXf0cCbZYZ5p9RhGdsPt0KcuX0WGmIV65_j28NL5nes6tbOvCs-HFliOXSpu33F4V9kVbjEuLtHJzzaAJjQPLGPyAnAQ7Bj1F_r2A2r_q1l2vGCbqnA)

![](https://lh7-us.googleusercontent.com/8r8pBgYaiGM-emWP8bHpyLTQLt3mR4vv42PvviLcwW8W9Jifz8T1OLE4Xe0TNwm236ncalQFU511opq4A7r1ZFUfy38vjw0R725bIa1f3e5izESl0Y5pnwgn4flXXK5TNnwrigYunuMRJyb2LfroSoY)

### Connecting with Mendix

To use your data in Mendix, do the following:

1. Download the PostgreSQL JDBC connector from [https://jdbc.postgresql.org](https://jdbc.postgresql.org) and place the .jar file in the *userlib* folder within your project folder. ![](https://lh7-us.googleusercontent.com/jJ3mu1i0VokV_VkUqg0NH_O8wa2NhH1UZ_SMr7CxNG1FAgZkLrOJsgQxLvGWfJLES-8Q1LdIIXj77unQYbDVb-RyF7fMZiHl3zIEDgKgKqzlYmCAa7mNj2BG_sxLKeNXHQC342VEcYaeQC_TGxlcSks)
2. Visit the Mendix Marketplace and download the Database Connector.

![](https://lh7-us.googleusercontent.com/M0nz9ZYfzJ7Mr37A3RIYBYc6TIS3_X6jGQquy_xPu58lNcqRh5l8oXfwHv6mKZz9WtHRaesx3eo3_k6tIPt_BhW2R-PNBNQN-jFJQ8vmjfP4UFF0DDezyaN8PlLWiyFMeCJlVLkxGjJxoZOL3xWrMFw)

![](https://lh7-us.googleusercontent.com/tvJ9jrJvjSLJ11l2JAByDt6cMM7fvDuN_-wnt4rlsFa0mO4977EiJM9Bm9cJC4dv0bQamuPa7STJ_y45FiMt1pnLfTiWwX7WlPSvvsHZOcM1TH946OUmzwkglrWJ4H4-jYdtQxB8Os69UNpBZex7g-E)
3. Insert the Database Connector into a microflow, as described in the Mendix documentation.
4. When configuring the action, provide the following values:
  - **Jdbc url:** jdbc:postgresql://[your-company.sightmachine.io:5432/tenant_storage](http://your-company.sightmachine.io:5432/tenant_storage)
  - **User name:** Your API key
  - **Password:** Your API secret

![](https://lh7-us.googleusercontent.com/cvWdAb5fpRhtzk4Y9wjt9wl-FUYvNBsi3b8xkmHdTCz3WEJEzVZjWz50Mhp6su6ZC2MWB09LPWRIxChqmzTwdVowV2s2k9I8mXbtC3SEUkhi99cJYZ4xlS-KA3ghyYGKxeWZQFZNHtklZfhK_2oGtzQ)

For more detailed information and assistance, refer to the full documentation available at [https://docs.mendix.com/appstore/connectors/database-connector/.](https://docs.mendix.com/appstore/connectors/database-connector/.)

## Accessing Workspaces

All non-archived workspaces are accessible with the ODBC connector. Unlike the current in-production workspace, which is accessible as the "sightmachine" schema, each deployed workspace has its own dedicated schema and can be accessed by Workspace ID.

### Accessing Non-Production Workspace Schemas

1. **Navigate to the Workspaces Page:** Open STRUCTURE, and then go to the Workspaces page to view a list of all available workspaces.
2. **Locate Workspace ID:** Each workspace is associated with a unique ID, positioned just below its name on the Workspaces page.
3. **Identify Workspace Schema:** The schema for a particular workspace is named **workspace_[ID]**. This naming convention remains consistent throughout the schema's lifetime.

#### Example:

For instance, if your workspace has ID 25, its schema is named **workspace_25**. This ensures a clear and predictable naming structure for easy identification.

#### Important Points to Note:

- **Production Schema:** When you are using the production “sightmachine” schema, the underlying data structures may change as workspaces are published as production.
- **Undeployed Workspaces:** Workspaces that have not yet been deployed, like workspace 17 in the provided example, do not have an associated schema.
- **Archived Workspaces:** When you archive a workspace, its schema is also removed. However, if you later restore an archived workspace, a new schema is automatically created for it.