Eagle's Process Manager offers a powerful and flexible way to populate your Data Mart. For example, you can design rules that automatically respond to changes in warehouse data to re-populate the appropriate tables in Data Mart, keeping the data warehouse and Data Mart in synch.
When you schedule a Data Mart build without using Process Manager, you must build data for every entity associated with every model. Process Manager gives you additional flexibility by letting you set up rules stating which models and entities to build. For example, your entities may be grouped in the daily workflow and ready for Mart processing at different times. Process Manager allows you to schedule different builds for groups of entities ready at different times, such as 1 a.m., and 3 a.m.
When you process the Mart using Process Manager, you can schedule runs of Data Mart event packages that contain one or more specified Data Mart schedules. You can also run a single schedule without an Event Package. This allows you to make use of Selective Fields if you want the event that kicks off Process Manager to populate only certain fields of the tables involved. To do this, set up and use a Data Mart selective build schedule configured to populate only your chosen fields. Consider the Batch Size setting in a Process Manager workflow. This is the number of entities that are submitted by a single Data Mart Manager engine. For Data Mart builds, batch size should not be set, in order to launch just one Data Mart Manager engine. Parallel processing is achieved as the Data Mart Manager engine launches multiple Model Manager engines, and each of those, multiple OLAP engines.
Manage space
Manage content
Integrations
0 Comments