Cloud Amplifier - Snowflake - Choose schema and custom DB and Schema names

chrissweeney92 · 2023-07-12T13:43:40+00:00

There was an error rendering this rich post.

For Cloud Amplifier on Snowflake, it would be helpful if we were able to:

Choose both the destination DB and Schema that the data lands in (rather than having to go only to the Domo managed DB and Domo manage schema "RAW_DOMO".
Be able to rename the DB and Schema that is generated when the connection is set up

The reason for this is that customer Snowflake instances contain more than just Domo datasets. In our example, our customer would like to have one Schema for each data source (e.g., one for Adobe, one for Google Analytics etc.). Not all of this data is added via Domo, but they want the Domo data to land in the same DB and schema as datasets added via a different method and they would like to be able to name this schema as the data source.

Find more posts tagged with

Snowflake

Submitted and awaiting review from product team

Cloud Amplifier

Status: Submitted and awaiting review from product team

Comments

akeating

We also need the option to exclude the DB and Schema from the dataset names instead of needing to rename each dataset individually.

jaeW_at_Onyx

When setting up a CA integration, we can see multiple warehouses and specify what operations take place in which warehouse. is it on the roadmap to be able to select the warehouse a query is executed on on a per dataset or per push down ETL basis?

for smaller tables we use xsmall warehouses and for larger workloads we would nee the option of choosing a different warehouse, but setting up an integration for each permutation of warehouse and data freshness check is unwieldy if not borderline untennable.