Dataset Storage vs. Database Connection

Matt_B

From the perspective of an FDI end-user concerned with saving their datasets, data flows, and workbooks in an optimal manner for scaling and long-term usage (access/sharing, reusability, space/costs, etc.), can you please explain the difference in Dataset Storage vs. Database Connection?

Any key insights to keep in mind or potential missteps to avoid when delineating Dataset Storage vs. Database Connection would be very helpful. Thank you

Sumanth V -Oracle

@Matt_B -

Here’s a quick breakdown of the differences between Database Connection and Dataset Storage in OAC to help with your decision:

Database Connection:

• Handles large datasets efficiently with optimized queries.
• Data remains in the external system, making it accessible outside OAC.
• Always reflects the latest data without requiring manual updates or refreshes.

Dataset Storage:

• Stores the dataset directly within OAC (Fusion Data Intelligence) after upload or transformation via a Data Flow.
• Faster for reporting and analysis since the data is cached in OAC.
• Limited to OAC users—external database queries are not possible.
• Requires manual updates when the source data changes unless scheduled refreshes are configured.

Hope this helps to make a decision based on your requirement!.