- UDAI places the data in the source systems.

- A set of views are defined for providing access the unified view to the clients / customers.

- Zero latency of data can be propagated from the source system.

- The generated consolidated data need not require separate storage space.

- Data history and version management is limited and applied only to the similar type of data.

- Accessing to the user data overloads on the source systems.

Look for the existence of the following items:

- Generic Data Models

- An Enterprise Data Platform

- Identify the Data Sources

- Selection of a MDM Product

- Implementation of a Customer Master Index or appropriate alternative

Following are the data integration factors:

- Sub set of the available data should be optimal. 

- Noise/distortion estimation levels because of sensory/processing conditions at the time of data collection.

- Accuracy, spatial and spectral resolution of data.

- Data formats, storage and retrieval mechanisms.

- Efficiency of computation for integrating data sets to reach the goals.

Following are the benefits of data integration:

- Makes reporting, monitoring, placing customer information across the enterprise flexible and convenient.

- Data usage is efficient.

- Cost Effective.

- Risk adjusted profitability management as it allows accurate data extraction.

- Allows timely and reliable reporting, as data quality is the prime technology for business challenges.

- The process of combining data from different resources.

- The combined data is provided to the users with unified view.

- Information from different enterprise domains are integrated – known as Enterprise Information Integration.

- Useful for merging information from different technologies among enterprises.

- The sub areas of data integration are 

1. Data Warehousing.

2. Data Migration.

3. Master Data Management.

- Scheduling and executing the batch jobs.

- Configuring, starting and stopping the real-time services

- Adapters configuration and managing them.

- Repository usage, Job Server configuration.

- Access Server configuration.

- Batch job publishing.

- Real-time services publishing through web services.

•  NO_CACHE – It is used for not caching values.


•  PRE_LOAD_CACHE – Result column preloads and compares the column into the memory, prior to executing the lookup.


•  PRE_LOAD_CACHE is used when the table can exactly fit in the memory space.


•  DEMAND_LOAD_CACHE – Result column loads and compares the column into the memory when a function performs the execution.


•  DEMAND_LOAD_CACHE is suitable while looking up the highly repetitive values with small subset of data.

Cascade:

- Cascade process involves taking values from various other prompts.

- The result is a single report.

- The result is used when a criteria is to be implemented.

Drill Through:

- Drill Through process is implemented when navigation from summary to detailed information.

- Drill Through has a parent and a child report.

- Data of another report can be seen based on the current details of data.