Data storage

LearningNinja

Hello,

I understand any data coming from files and output datasets from DOMO ETLs shall store data in DOMO Cloud. Any of the following shall also store in DOMO Cloud?

1. DataFlows
2. SQL View (DOMO)
3. Adrenaline Transform

What if I use federated connection as my connector? or an API to retrieve data from source and leverage any of the above tools?

ArborRose

1. DataFlows:

• Data Storage: Yes, DataFlows (which include Magic ETL, SQL DataFlows, and Python/R DataFlows) store the output datasets in the Domo cloud. When you run a DataFlow, it processes the data and outputs the result as a new dataset in Domo, which is stored in the Domo cloud.

2. SQL View (Domo):

• Data Storage: Yes, SQL Views in Domo also store the data in the Domo cloud. When you create a SQL View, it materializes the result as a dataset in Domo, which is stored in the Domo cloud.

3. Adrenaline Transform:

• Data Storage: Yes, Adrenaline Transform is Domo’s in-memory query engine, which processes data and stores the resulting dataset in the Domo cloud. The results of any transformation are stored as a new dataset in the cloud.

4. Federated Connection:

• Data Storage: No, when using a federated connection, the data is not stored in Domo. Instead, Domo queries the data directly from the source when needed. The federated connection allows you to use data from external sources without moving it into the Domo cloud, meaning that it remains in its original location and is not duplicated in Domo.

5. API to Retrieve Data from Source:

• Data Storage: Yes, if you use an API to retrieve data from a source and then leverage any of the above tools (DataFlows, SQL View, Adrenaline Transform), the data retrieved via the API will be stored in the Domo cloud. The API pulls the data into Domo, and once it’s in Domo, any transformations or operations performed on it will result in the data being stored in the Domo cloud.

Summary:

• Stored in Domo Cloud:
  • DataFlows
  • SQL View (Domo)
  • Adrenaline Transform
  • API data pulled into Domo
• Not Stored in Domo Cloud:
  • Federated connections (data remains in its original source and is not stored in Domo).

If the goal is to avoid storing data in Domo’s cloud, federated connections are the best option. Otherwise, any data processed by Domo's internal tools (like DataFlows, SQL Views, etc.) will result in storage within the Domo cloud.

ArborRose

1. DataFlows:

• Data Storage: Yes, DataFlows (which include Magic ETL, SQL DataFlows, and Python/R DataFlows) store the output datasets in the Domo cloud. When you run a DataFlow, it processes the data and outputs the result as a new dataset in Domo, which is stored in the Domo cloud.

2. SQL View (Domo):

• Data Storage: Yes, SQL Views in Domo also store the data in the Domo cloud. When you create a SQL View, it materializes the result as a dataset in Domo, which is stored in the Domo cloud.

3. Adrenaline Transform:

• Data Storage: Yes, Adrenaline Transform is Domo’s in-memory query engine, which processes data and stores the resulting dataset in the Domo cloud. The results of any transformation are stored as a new dataset in the cloud.

4. Federated Connection:

• Data Storage: No, when using a federated connection, the data is not stored in Domo. Instead, Domo queries the data directly from the source when needed. The federated connection allows you to use data from external sources without moving it into the Domo cloud, meaning that it remains in its original location and is not duplicated in Domo.

5. API to Retrieve Data from Source:

• Data Storage: Yes, if you use an API to retrieve data from a source and then leverage any of the above tools (DataFlows, SQL View, Adrenaline Transform), the data retrieved via the API will be stored in the Domo cloud. The API pulls the data into Domo, and once it’s in Domo, any transformations or operations performed on it will result in the data being stored in the Domo cloud.

Summary:

• Stored in Domo Cloud:
  • DataFlows
  • SQL View (Domo)
  • Adrenaline Transform
  • API data pulled into Domo
• Not Stored in Domo Cloud:
  • Federated connections (data remains in its original source and is not stored in Domo).

If the goal is to avoid storing data in Domo’s cloud, federated connections are the best option. Otherwise, any data processed by Domo's internal tools (like DataFlows, SQL Views, etc.) will result in storage within the Domo cloud.