Please enable JavaScript.
Coggle requires JavaScript to display documents.
Cattle Owner DW, * (SELECT td.TagUuid, td.CurrentEID, td.CurrentTagNumber,…
-
*
SELECT td.TagUuid, td.CurrentEID, td.CurrentTagNumber, c.Uuid, c.Company
-
-
-
-
-
FY1
Next Gen DB
-
Limit data that flows over - buyers, contracts, etc
-
-
-
FY12
-
BG - don't have CC subscription
Locations within an instance - that is owned by the Cattle Owner - then all data can flow through
-
ALCC ETL
ALCC Integrated DW
-
QUESTIONS
1) How does this work with the OLD ETL (Current V1) and the new table structure ETL (Cattle Owner)?
2) How many versions of a DW are there for a Cattle Owner? $$$$
-
-
-
-
-
- Only cattle that owner owns.
Support of CO DW
- Table Driven setup - how to know where a step failed ?
- Is this ability in the dev plan (roadmap)?
- Integration with App and partnerships - what setup is required to develop CO DW?
owners
- Cattle Owner
Arrival groups have a bunch of reference data (City, state, region, nationality)
- How would you know what a CO should see - what ever they attache to their purchase
*Of the dims and facts which one has to be limited down to a cattle owner (what is global and tennant based)
-
-
-
-
*Subscription ID between NextGen and V1 Database system <> then the system owners are different and we have to limit the data & CO specific objects/data must flow from NG thru ETL into CO DW
SID between NG and V1 are = then all data can flow through
-