Skip to main content
Solved

ODX same source but different tables based on environment

  • 5 June 2024
  • 1 reply
  • 29 views

Hello,

Our team has recently started shifting from using Business Units as our data ingestion approach towards ODX server.

Our project contains 3 environments (Dev, Test, Prod). All of our data providers give us 2 tables per dimension/fact (e.g. dim.user and dim.user_qa etc.) and we store them in 2 separate databases (Datastore and Datastore_qa respectively) with exactly same names (dim.user).

We have a following setup in place implemented using “Environment properties”:

Environment Source database
Dev Datastore_QA
Test Datastore_QA
Production Datastore

 

This way contents of dim.user table are loaded from Datastore_QA database on Dev and Test environments, and from Datastore database on Production environment.

 

Is there any way to achieve the same result utilizing ODX server as data ingestion approach?

 

Hopefully this makes sense, thank you!

 

1 reply

Userlevel 6
Badge +7

Hi @gediminas.juskenas ,

 

in the 20.10.x release you will mostly work with one ODX Server loading production data and use this for all environments. As you can only have one ODX Server linked to a project, it is not possible to use exactly the same setup as you would in a BU situation in that TimeXtender release. You can use a the sandbox environment or second ODX Server project to facillitate other projects or test things.

In the 6xxx release you can have as many ODX instances as you want and you manage the ODX instance a DWH is mapped from as part of the promotion process.

Reply