Use multiple marts to create, maintain, and use more than one schema for your Data Marts. Different schemas share a single Eagle data warehouse as their source of data. You control all of your multiple Data Marts from the Data Mart component of PACE.
Anchor | ||||
---|---|---|---|---|
|
The multiple marts option offers you many possibilities for information delivery. They can help you scale your data delivery as your business grows.
However, multiple marts add complexity along with flexibility, and you should use them only after careful analysis and planning. Each mart is configured and updated independently. There is no support in the product for sharing physical tables across marts, so there may be duplication of data that places additional demands upon system resources in the build process. When duplicate data is built, some mart content can temporarily get out of synchronization. Given that each mart is configured separately, it is possible to select a different field attribute for a field in one mart than was selected for that field in another mart. Using the Copy Model feature can greatly mitigate this risk. In addition, firmwide reporting is usually done from just one mart, so some level of data duplication may be unavoidable.
Anchor | ||||
---|---|---|---|---|
|
You use multiple marts for a variety of reasons, including:
...
These are some of the considerations involved in the decision to use multiples. Eagle Global Service and Support can help each client evaluate this decision and achieve an overall design that takes best advantage of this powerful capability.
Anchor | ||||
---|---|---|---|---|
|
Each mart instance is a distinct destination to which the Data Mart engines can push data. You can maintain as many marts of any of these types as you want. Possible types of destination schema include:
...