|
Nr. |
Feature |
EIQ Products |
Data Warehouses |
Conventional Federated Adapters |
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 conventional federated
adapters |
|
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 conventional federated adapters
– 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
|
Results when data sources
unavailable
|
+ |
+ |
- |
|
19 |
Data remains at source |
+ |
- |
+ |
EIQ Products advantages
over data warehouses – same as conventional federated adapters |
|
20
|
User-level access to data sources
|
+ |
- |
+ |
|
21 |
Latest data available |
+ |
(-)[12] |
+ |
|
22 |
Drill-down capabilities |
+ |
(-)[13] |
+ |
|
23 |
No index or query load
on data source systems |
(+)[14] |
+ |
- |
Data warehouses
advantages over EIQ Products and conventional federated adapters |
|
24 |
Data source owners not
aware of queries |
(+)[15] |
+ |
- |
|
25 |
Archive |
(-)[16] |
+ |
- |
|
26 |
Good for standard application data
sources |
(+)[17] |
- |
+ |
Conventional
federated
adapters
advantages over EIQ Products and data warehouses |
|
27 |
No need for data or
index update process |
(-)[18] |
- |
+ |
|
28 |
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 individual column reindexing
[10]
Conventional federated adapters can
accommodate minor changes, but not to the extent that
EIQ Products can
[11]
Many conventional federated adapters
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 servers 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 servers and minimal storage for
conventional federated adapters
