--- title: "Connecting with an ODBC" slug: "connecting-with-an-odbc" updated: 2026-03-26T19:32:08Z published: 2026-03-26T19:32:08Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Connecting with an ODBC ## Overview To further the integration abilities with **External****Databases**, Decisions provides the ability to connect to **ODBC Databases**. [ODBC's](https://docs.microsoft.com/en-us/sql/odbc/reference/what-is-odbc?view=sql-server-ver15#:~:text=To%20the%20end%20user%2C%20it,specification%20for%20a%20database%20API.) (Open Database Connectivity) are APIs that allow an application to utilize information from different **Database Management Systems**. Designers integrate with any Database supporting ODBC not already built into Decisions through the **ODBC Metadata Flow**. Designers may specify the unique characteristics of the Database's type to connect and collect the Database's Metadata for creating Tables, Reports, etc., within Decisions. Once successfully connected, the new Database automatically appears as an option in future Decisions Integration wizards on the device. Once a Database is introduced, components to **Query**, **Insert**, or **Update** data to or from the Database within the **Flow****Designer**can be used similarly to other integration methods. The following document details how to establish a connection with an ODBC integration. --- ## Example The following example demonstrates how to Integrate with a Sybase ODBC Database. To do so: 1. From the **Decisions****Studio**, navigate to **System > Integrations > Databases**. 2. From the **Global****Action****Bar**, click the CREATE CONNECTION button. 3. From the **Database****Integration**window, provide a **Connection****Name**. Then, select ODBC from the **Database****Type**drop-down. Additional Information on Connection NameNote that the Connection Name cannot contain any spaces. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-02_13h36_50.png) 4. Provide a valid connection string following the: **Driver={ODBC Driver's Name Here};server=nameOfTheServer;port=portNumber;db=databaseName;uid=login;pwd=passwor****d;database=databaseName;schema=schemaName;**format. Then click PICK OR CREATE ODBC DB TYPE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-02_13h38_10.png) 5. PICK the Flow that corresponds with the Database (in this case **Sybase** **ASE**), and click TEST to test the connection. Then, click OK to save the Integration and exit. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-02_13h38_52.png) --- ## Pre-built ODBC Metadata Flows Decisions installations come with pre-built OBDC Metadata Flows for the following Databases: - Access - Netezza IBM - Redshift AWS - SAP SQL Anywhere - Sybase ASE - Databricks - Users can create an external database connection to use with their stored tables and views within Databricks. **Procedures are not supported.** --- ## Note on Building a Custom ODBC Metadata Flow Each Database and its ODBC Metadata Flow is Inherently UniqueWhen constructing a custom ODBC Metadata Flow, it is important to remember that not all Databases require nor provide the same information to connect; some Databases may only use a specific combination of Procedures, Tables, or Views Data Types. Unused Data Types should be set to the **Ignore**mapping type to proceed with the connection. The example zip folder demonstrates an ODBC Metadata Flow integration to Amazon Athena, which also features an unused Data Type: Procedures. Please download the file and import it to your Decisions instance to reference where the Ignore mapping type occurs. [Example[AthenaCustomODBCMetadataFlowSample].zip](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Example%5BAthenaCustomODBCMetadataFlowSample%5D.zip) Custom ODBC Metadata Flows is a flexible solution for connecting to a Database that does not have built-in ODBC support in Decisions**.** To accomplish this goal, ODBC Metadata Flows contain the credentials for Database access while also collecting the necessary data types and Metadata for use in the platform. Given the elasticity of ODBC Metadata Flows, each is highly unique due to the target Database for integration in addition to considering the Designer's goals. Additional Info on ODBC Metadata Flow ConfigurationThe essential steps when building a custom ODBC Metadata Flow include**Create Data,****R****aw SQL**, **Add Item to List, List Mapping Step,**and **ForEach**steps. However, additional Elements, such as Rules, Truth Tables, etc., may be applicable depending on the Database and/or the Designer's goals. Some built-in ODBC Metadata Flows contain these, so it is recommended to view them as a reference. An ODBC Metadata Flow starts two Create Data steps: 1. The first Create Data step creates lists to be populated by the Database with the **DBFullTableInfo**Data Type.Note that a list was not constructed for Procedures since Athena does not utilize it.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-17_15h44_24.png) 2. The second must declare the **connectionString**to the Database.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-17_15h44_56.png) 3. After these, a series of **Raw SQL******steps gather specific Metadata through a loop that then adds the desired data to a list. This command is specific to the language of the Database. Once complete, the next Raw SQL command loop begins. 4. After all loops are completed, the **End Step**outputs the data lists for the Database's Procedures, Tables, and Views Metadata. Again, since Athena does not produce Procedures, its input mapping type is set to **Ignore**. --- ## After Connection 1. Once integration with an **ODBC**has been appropriately established, users may then Integrate with its respective **Database****Tables** or utilize its respective **Flow**steps in the Flow Designer by navigating to **Toolbox > INTEGRATION > [NAMEOFINTEGRATION] > [TABLE].** Additional Information and Resources For more information on how to integrate with Database Tables, see [Integrate with Database Table.](https://documentation.decisions.com/v9/docs/integrate-with-database-table) ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-17_15h46_38.png)