Ease Of Management Within ODI.
Overall Satisfaction with Oracle Enterprise Data Quality
Oracle Enterprise Data Quality (OEDQ) helped my organization to define Data Quality issues from a business perspective by business users and ability to manage those issues within our ETL tool (Oracle Data Integrator - ODI).
Pros
- Ease of management within Oracle Data Integrator (ODI) and effectivity of EDQ Director
- Ease of installation with web based client.
- Data Quality issues solved quickly, easily and jobs are controlled within Oracle Data Integrator (ODI) seamlessly.
- Setup is straightforward. Java web application (OEDQ Director) helped us for not installing any client application.
Cons
- Mobile support and mobile app can be implemented, since business users generally prefers to work with not only their laptops, but also mobile phones or tablets.
- Data profiling could be standalone option instead of OEDQ Director. A business user generally wants to see the format or templated counts or other aggregations based on a full dataset.
- Data Quality issues solved quickly, easily and jobs are controlled within Oracle Data Integrator (ODI) seamlessly.
- Business users created their data quality packages and those packages are called from Oracle Data Integrator easily and merged into data warehouse.
- OEDQ jobs can be created by not only IT teams, but also business teams. That is why we called a "DQ job is not a part of our development, it is a part of our DWH solution".
- Trillium Data Quality and SAS DataFlux
Trillium and SAS DataFlux was considered but not having in-ETL management and licensing cost.
Comments
Please log in to join the conversation