Remote Table

A remote table in Dengage CDP is a table from an external database owned by a client, which Dengage CDP can access to get data.

A "Remote Table" in Dengage CDP (Customer Data Platform) refers to a feature where the table itself resides on a separate database, external to the primary database of the CDP. Here's a detailed explanation of how this feature works:

In Dengage CDP, a remote table is initially configured to mirror the structure of the corresponding table in the external database. This configuration is facilitated through a CDP interface detailed in the subsequent section. This definition enables Dengage to comprehend and engage with the data as though it were housed within its own local database.

Upon mirroring the structure, the CDP provides an Interactive Segment interface Segments that allows users to access and interact with the remote table. This interface enables users to perform various operations, such as filtering and querying data, without needing direct access to the external database. In summary, by setting up a remote table, users can access remote data without the need to write SQL queries.

The remote table feature is designed to be efficient and scalable because it eliminates the need to transfer all external data into the Dengage system. Transferring and continuously synchronizing such data can be problematic due to the sheer volume and the dynamic nature of updates. Instead, by allowing queries to be executed directly on the remote database, the data remains where it is stored, thus avoiding the complexities of data migration and synchronization. This setup ensures that the data is instantly available for use through the CDP interface without any IT intervention, facilitating real-time data access and manipulation for marketing and analytical purposes.

In summary, the Remote Table feature in Dengage CDP extends the platform's data handling capabilities by enabling seamless integration and interaction with data stored in external databases. This allows users to perform data-intensive operations remotely while utilizing the analytical tools and user-friendly interface of the CDP.

👍

Supported Databases

Dengage CDP supports Oracle, Google BigQuery and Microsoft MSSQL, Azure SQL Data Warehouse and very soon Amazon Redshift.

How to create a remote table

Go to Data Space > Tables and click +New

Click Remote Data Table. Available Remote Sources will be shown like below.

Available Remote Sources

Available Remote Sources

Step 1️⃣: The platform will present all available remote data sources to the user. Choose the remote data source from which you wish to add a table.

🚧

Prerequisites

Remote Source definitions must be established beforehand. Currently, Dengage CDP supports Oracle, Google Big Query and Microsoft MSSQL (Azure Data warehouse) and very soon Amazon Redshift.

Step 2️⃣: The platform will present all database schemas under that Remote Source like below

Database schemas under Remote Source

Database schemas under Remote Source

❗️

Required Permissions

Depending on the type of Remote Source, the necessary permissions must be granted to list schemas and tables within those schemas. Alternatively, the Pull with table name option can be used to directly reference the table.

Step 3️⃣: The platform will show tables under the schema selected.

Tables under the schema

Tables under the schema

Step 4: Select the columns to create virtual relationship on Dengage CDP and select contact_key column to connect to master_contact table in Star Schema Star Schema: Relational Database

Now, the remote table is connected to Dengage CDP's Star Schema relationship network and this table can be used in Interactive Segments directly without writing SQL code to fetch data from Remote Sources.

Select columns of the remote table and create contact_key relation to master_contact table

Select columns of the remote table and create contact_key relation to master_contact table

🚧

Contact key column

Contact key column of remote table has to be TEXT and NOT NULL in order to be selected as a Contact key column!

📘

Related Table > master_device

A master_device relationship can also be established. Suppose you have billions of events in your Google Big Query keyed to device_id. You can link this table to your master_device table, enabling direct audience targeting based on device behaviors.

Remote tables on Star Schema

Remote tables are represented with distinct logos in a Star Schema when properly connected. For instance, the below are two tables, one from Oracle and one from Google Big Query on Star Schema

An oracle and google bigquery table connected to Star Schema

An oracle and google bigquery table connected to Star Schema

👍

Table Filter

Since these tables are connected on Star Schema, you can use these tables directly in your Interactive Segments by Table Filter filtering.

🚧

License

This feature is enabled with Relational Database feature in CDP. You need to buy this license to use Remote Tables on your interactive segment queries.