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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 755 Beast Mode
- 61 App Studio
- 41 Variables
- 693 Automate
- 178 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive