Data Warehouse Modeling
Hello,
We just started up with Domo, and I am converting from Sisense B.I. platform.
In the Sisense platform, everything is in Cubes and relatively siloed off from one another unless you specifically linked them. Which worked well for our use case.
Before I dive headfirst into converting things I wanted to get a feel for the modeling in Domo. I like the notion of siloing things off, so things don't have the potential to bleed over. As our company does work for many clients, some whom are direct competitors of one another. So I want to mitigate the possibility of cross-talk as much as possible. Our rep made mention of something called 'Mini domos' but didn't elaborate on all that much.
So I am wondering if it would make more sense to try and silo things off. Of have the common data sources such as out Mysql tables. And then use ETL to create Datasets that are filtered per client with naming conventions
Client A-Base
Client A-Billing
Client B-Base
Client B-Billing
Etc...
Just looking to minimize crosstalk as much as humanly possible.
Thanks!
James (JT)
Categories
- 7.7K All Categories
- 5 Connect
- 921 Connectors
- 244 Workbench
- 479 Transform
- 1.8K Magic ETL
- 60 SQL DataFlows
- 446 Datasets
- 49 Visualize
- 202 Beast Mode
- 2K Charting
- 8 Variables
- 2 Automate
- 349 APIs & Domo Developer
- 82 Apps
- Workflows
- 14 Predict
- 3 Jupyter Workspaces
- 11 R & Python Tiles
- 241 Distribute
- 59 Domo Everywhere
- 241 Scheduled Reports
- 15 Manage
- 36 Governance & Security
- 37 Product Ideas
- 1.1K Ideas Exchange
- 2 Community Forums
- 15 Getting Started
- 2 Community Member Introductions
- 50 Community News
- 18 Event Recordings
- 579 日本支部