 |
What is QueryObject? |
 |
What
are the benefits in using QueryObject as Data management
Infrastructure? |
 |
What
kind of application can be developed with QueryObject? |
 |
Why does QueryObject perform and scale so
well? |
 |
Which are the key advantages QO ensures? |
 |
What are
supported standards? |
 |
What
front-end tools can be used to access the QueryObjects?
Which have been certified as QO compatible? |
 |
Is it possible to access a QueryObject
using a proprietary front-end tool? |
 |
What are the QO proprietary processes? |
 |
The security of the information contained
into a QO is preserved also if it is detached from the
host server and distributed physically via e-mail or
CD-Roms |
 |
How much time does it take to train a user
on QueryObjects ? |
 |
Which vertical market solutions can be
(have been) developed with QO? |
|
| What is QueryObject? |
| QueryObject is
an analytical data management technology that boosts
existing big data infrastructures’ performances and is
comprised of: |
|
 |
An exact, complete, compressed, and de-normalized image
of a selected portion of a data set read from any
combination and collection of supported data sources; |
|

|
A dense, materialized aggregated view of data copy built
with highly efficient indexing methods and containing
pre-calculated, ultra-efficient, and portable results
for ALL possible queries on data copy; |
 |
Can be accessed by any kind of BI
toolkit; |
 |
A set of dynamic correlation keys (through primary and
secondary indexes) between aggregated views and DB copy |
|

|
|
What are the benefits in using QueryObject as Data
management Infrastructure? |
 |
Compression |
 |
Speed of generation |
 |
Scalability |
 |
High Performance Access |
 |
Simple, low cost, and comprehensive dynamic and static
reporting |
 |
Openness to any type of Data Source (Oracle, SQL*Server,
DB2 etc.); |
 |
Open access from any type of delivery tools (BO, Brio,
Cognos, Data Beacon, MS Office, etc.); |
 |
Open access from and to any type of standard (XML, SOAP,
ODBC, JDBC, etc); |
 |
Effective long term time series analysis; |
 |
No DB management system required |
 |
Platform portability, mobility |
| . |
| What
kind of application can be developed with QueryObject? |
|
|
QueryObject has been successfully applied to the
following markets: |
|

|
Data
Integration: |
|
CDI
(Customer Data Integration) projects for Sales &
Marketing, Sales Force Automation; Customer
Profiling |
|
Pre/Post
Aggregation Processing |
|
High Volume
Data Movement |
|
Multiple
Data Sources Access. |
 |
Business Intelligence: |
|
Extreme BI
projects; |
| |
Data Mart Solutions; |
|
Historical Data
Management Solutions; |
| |
Business Intelligence on the fly; |
| |
Disconnected-wireless Business
Intelligence; |
| |
Infrastructures and Frontend tools
Performances crisis lifeguard; |
 |
Data Services. |
| . |
Data Exchange Services; |
| |
Data Services Provisioning
solutions; |
| |
|
|

|
|
Why does QueryObject perform and scale so
well? |
|
"Using proprietary mathematical algorithms we've
solved the Big Data storage and its fast retrieval
issues". |
|

|
|
Which are the key advantages QO ensure? |
|
QueryObject provides “Plug&Play” integration with existing Data Management system and Information Delivery
applications.
On the back-end side, QueryObject provides seamless connectivity to any source data
(relational, hierarchical, flat, transactional,
warehouse, mainframe).
On the front-end side, QueryObject provides a deployment interface to leverage any existing or new analysis and reporting tool in the enterprise in a web or
client/server infrastructure.
Below main advantage provided: |
 |
Seamless integration into existing infrastructure |
 |
Low TCO, (management, hardware, support & development) |
 |
Selective and secure distribution to both the connected
and disconnected information consumer |
 |
Scalability up to the largest Terabyte class data
sources |
 |
Speed of implementation (weeks instead of months). |
 |
Speed of delivery (the information available when it's
needed). |
 |
Speed of access (seconds instead of minutes or hours). |
 |
Fully interactive |
 |
Fully customizable |
 |
Multi-channel support |
|
|
|

|
| What are
supported standards? |
 |
ODBC |
 |
JDBC |
 |
OLE-DB |
 |
XML |
 |
SOAP |
 |
DES |
|
|
|

|
|
What front-end tools can be used to access the
QueryObjects? Which have been certified as QO
compatible? |
|
Any ODBC compliant front-end tool can be used to access
the QueryObjectst. Follow this
link to
have a list of certified thirdy party tools. |
|

|
|
Is it possible to access a QueryObject using a
proprietary front-end tool? |
| Yes, we
provide proprietary programmers interfaces in C and
Java, as well as standards based interfaces suh as ODBC,
JDBC, OLE-DB, XML. |
|

|
| How can QO be considered a product complementing BI toolkits such as Business Objects or Brio? |
| It can be used as the back-end optimized information store to support ‘speed-of-thought’ analysis on your data using the mentioned tools as a front end. |
|

|
| What front-end tools cab be used to access the QueryObjects? Which have been certified as QO
compatible? |
| Any ODBC compliant front-end tool can be used to access the
QueryObjects. We have certified as compatible Brio, Business
Objects, Cognos PowerPlay, Crystal Reports, Informatica Power
Analyzer, Microsoft Excel, Microstrategy, Pilot, SPSS. |
|

|
| Is it possible to access a QueryObject using a proprietary front-end
tool? |
| Yes, we provide proprietary programmers interfaces in C and Java, as well as standards based interfaces suh as
ODBC,JDBC,OLE-DB, XML |
|

|
|
What are the QO proprietary processes? |
| Proprietary
access API to QO. The entire data load, data processing
is a proprietary combination of using some well known
and best-of-breed approaches/algorithms. |
|

|
|
The security of the information contained into a QO is
preserved also if it is detached from the host server
and distributed physically via e-mail or CD-Rom? |
| Yes, you can
use LDAP servers for authenticating user/group logins;
if the server is not available, you can fallback on the
user accounts information stored in the QueryObject own
security management file. |