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
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 282 Workbench
- 3 Cloud Amplifier
- 4 Federated
- 2.8K Transform
- 86 SQL DataFlows
- 548 Datasets
- 2.2K Magic ETL
- 3.2K Visualize
- 2.3K Charting
- 542 Beast Mode
- App Studio
- 26 Variables
- 566 Automate
- 134 Apps
- 411 APIs & Domo Developer
- 21 Workflows
- DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 344 Distribute
- 86 Domo Everywhere
- 257 Scheduled Reports
- 1 Software Integrations
- 85 Manage
- 84 Governance & Security
- 6 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 81 Community Announcements
- 4.8K Archive