Embrace overview

Using Embrace, you can perform live queries on external databases.

If your company stores source data externally in data warehouses, you can use ThoughtSpot Embrace to directly query that data and use ThoughtSpot’s analysis and visualization features, without moving the data into ThoughtSpot.

Embrace supports the following external databases:

  • Snowflake

  • Amazon Redshift

  • Google BigQuery

  • Microsoft Azure Synapse

  • Teradata

  • SAP HANA Beta

To enable Embrace, contact ThoughtSpot support.

How it works

You create a connection to the external database, choosing the columns from each table that you want to explore in your live query. Primary key and foreign key relationships are imported along with the primary and foreign key tables. If there are any joins in the tables of your connection, they are also imported. After your connection is complete, it becomes a linked data source in ThoughtSpot that allows you to query the external database directly. It’s easy to apply transformations and filter the data also.

Key benefits

  • Set up and deploy ThoughtSpot faster by connecting directly to the external database.

  • Eliminate the need to move data into ThoughtSpot for analysis.

  • Centralize data management and governance in the external database.

  • Save significant time and money by avoiding ETL pipelines.

  • Connect to multiple external databases.

Limitations

Feature availability in Embrace

Feature Name Falcon Embrace

Simple Search and Complex searches:Versus, Inline Subquerying, Growth

Search Suggestions for column names and values

Headlines that summarize tables

All chart types and configurations

Spot IQ: Instant insights, Did you know?,Pinboard insights, Analyze

SpotIQ Monitor Headlines

Table and Column remapping through Scriptability

Custom calendar

Materialized view

Function availability in Embrace

The following matrix compares the specific function support across the different databases of Embrace. Functions not listed here have full support.

Function Snowflake Amazon Redshift Google BigQuery Azure Synapse Teradata SAP HANA

SOUNDS_LIKE

STRING_ MATCH_SCORE

EDIT_DISTANCE_WITH_CAP

APPROX_SET_CARDINALITY

COUNT_NOT_NULL

SPELLS_LIKE

EDIT_DISTANCE

MEDIAN

PERCENTILE

Data type availability in Embrace

The following matrix captures the specific data type support limitations across the different databases of Embrace. Data types not listed here have full support.

Data Type Snowflake Amazon Redshift Google BigQuery Azure Synapse Teradata SAP HANA

BINARY

VARBINARY

GEOMETRY

BYTES

DATETIMEOFFSET

Additional specific exceptions

The following list captures the specific limitations across the different databases of Embrace. Databases not listed here have full support.

General: all databases
Sample values

Embrace does not internationalize sample values in tables.

Google BigQuery
Join support

Google BigQuery does not support PK-FK joins. Therefore, when using Embrace, you must create joins explicitly in ThoughtSpot.

Partitioned tables

When running a query on a partitioned table with the Require partition filter option enabled, you must specify the WHERE clause. Without a WHERE clause specified, queries generate an error. To ensure that the query on such tables honors the partition condition, you must create a worksheet filter in ThoughtSpot.

Azure Synapse

Azure Synapse supports up to 10 IF THEN ELSE statements in a single query.

Azure Synapse does not support foreign keys, so no PK-FK joins can be defined in Synapse.

Teradata

Teradata does not support the function: AGGREGATE_DISTINCT.

Teradata does not support the following data types: JSON, INTERVAL, VARBYTE, BLOB, CLOB, PERIOD, XML, GEOSPATIAL.

SAP HANA

SAP HANA does not support the following functions: PERCENTILE, AGGREGATE_DISTINCT, SPELLS_LIKE, EDIT_DISTANCE.

SAP HANA does not support the following data types: BLOB, CLOB, NCLOB, TEXT, POINT.

SAP HANA does not support calculation views with mandatory input parameters. If you need to use calculation views in ThoughtSpot, you must remove the mandatory parameter requirement.

Next steps