WhamTech - 27-point comparison of data integration technologies

27-point comparison of data integration technologies

Comparison between EIQ Products and other approaches ranked by advantage to EIQ Products:

Nr.	Feature	EIQ Products	Data Warehouses	Federated Database Systems	Comment
1	Minimal implementation time	ü	û	û	Unique to EIQ Products
2	Quickly add new data sources	ü	û	û
3	Flexibility of use and users	ü	û	û
4	Actively monitor data sources	ü	(û)[1]	û	EIQ Products advantages over data warehouses and federated database systems
5	Full text search	ü	(û)[2]	û
6	Unlimited query options and performance	ü	(ü)[3]	û
7	Denormalized views	ü	(ü)[4]	û
8	Link mapping and analysis/data mining	ü	(ü)[5]	û
9	No major schema transforms	ü	û	(ü)[6]
10	Can write to data sources	ü	û	(ü)
11	Row, column and data element security	ü	(ü)[7]	(û)[8]
12	Data source changes readily made	(ü)[9]	û	(û)[10]
13	Clean and useable data	ü	ü	û	EIQ Products advantages over federated database systems – same as data warehouses
14	Consistent and multiple indexes and types	ü	ü	û
15	Almost any data source	ü	ü	û
16	Do not install anything on data source systems	ü	ü	(û)[11]
17	Pre-aggregated and pre-calculated fields	ü	ü	û
18	Data remains at source	ü	û	ü	EIQ Products advantages over data warehouses – same as federated database systems
19	User-level access to data sources	ü	û	ü
20	Latest data available	ü	(û)[12]	ü
21	Drill-down capabilities	ü	(û)[13]	ü
22	No index or query load on data source systems	(ü)[14]	ü	û	Data warehouses advantages over EIQ Products and federated database systems
23	Data source owners not aware of queries	(ü)[15]	ü	û
24	Archive	(û)[16]	ü	û
25	Good for standard application data sources	(ü)[17]	û	ü	Federated database systems advantages over EIQ Products and data warehouses
26	No need for data or index update process	(û)[18]	û	ü
27	No additional system cost	(û)[19]	û	(ü)[20]

[1] Real-time data warehouses only
[2] Typically, data warehouses do not have full text search
[3] Typically, additional databases or data marts are used for unlimited query options and performance
[4] Typically, additional databases or data marts are used for denormalized views
[5] Typically, additional databases or data marts are used for link analysis/data mining
[6] No major schema transform if flat front-end schema used, e.g., GJDXDM and NIEM in government
[7] Data owners relinquish control over their data. Only one or two DBMS vendors provide this level of security
[8] Only if data sources provide this level of security (see footnote 7)
[9] EIQ Products can accommodate some changes, e.g., indexes can be used to create new indexes; however, fundamental changes may require reindexing
[10] Federated database systems can accommodate minor changes, but not to the extent that EIQ Products can
[11] Many federated database systems require specialized connectors and/or special access that requires installation of something on data source systems
[12] Only for real-time or active data warehouses
[13] Can be implemented in data warehouses, but not typical
[14] Small overhead on data source system when retrieving final result-set data
[15] Data source system receives low-level request for specific records only – not the query that resulted in them
[16] EIQ Products can (a) store results data, (b) be configured to work with mirror-image copies of original data sources that act as archives; this complies with Sarbanes-Oxley and other regulatory requirements – note: data warehouses are not considered original data source copies, and (c) maintain an index to archives
[17] Can use application vendor or third-party change data capture (CDC) capability or results level indexes
[18] Only index update process, but not data
[19] Typically, separate CPU for query processing and storage for indexes for EIQ Products, but not storage for data or separate DBMS to maintain as for data warehouses
[20] Typically, separate CPU and minimal storage for adapters for federated database systems

Send To Printer
Close Window