DRAFT This page is not complete – if you need information on this topic, please contact us
The primary goal of DAX Optimizer is to analyze models. DAX Optimizer stores models and related analyses results with the following hierarchy:
The region is the first hierarchical level and corresponds to the physical location of the data.
An account can have models in different regions, but only one region is active for the current DAX Optimizer session of the user. You can change the active region by using Switch Region in the account settings.
Choosing the regions is important because you cannot move models from one region to another. If you need to move a model to a different region, you must:
- Download the VPAX files of the model
- Create the model in the new region
- Upload the VPAX files for the model in the new region.
The workspace is a container of models that can be shared with other users.
A workspace is local to a region, must be created explicitly by the user, and cannot be moved to a different region.
Every user has a private personal workspace called My Workspace that cannot be shared and renamed. There is a personal workspace for every region: when the user switches the active region, the personal workspace is switched accordingly.
The model is the object that contains all the analyses made on different versions of the same Tabular model.
A model is created in a workspace and can be moved to a different workspace within the same region.
A model can be shared with other users by using the Share operation.
A new model always has an initial version corresponding to the VPAX file uploaded by the user.
A version includes the result of the analysis only after executing a run.
The version name is defined by the client tool used to upload the VPAX file. The standard client of DAX Optimizer uses a sequential number (v1, v2, …). Other clients could use different names.
The result of a Run includes the DAX Optimizer engine version used. If a new version of the DAX Optimizer engine is released, the user might re-run the analysis to get updated results. Therefore, multiple results (Runs) could be available for a single version, and they are identified by the date and time of the Run execution. However, we suggest always running the analysis with an updated version of the VPAX file in a new version, obtaining no more than one Run per version.