 |
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 event data management platform that boosts
existing big data infrastructures’ performances. The QueryObject data set is
comprised of: |
|
-
|
An exact, complete, compressed, and de-normalized image
of input data sources; |
|
-
|
A compressed materialized aggregated view of data; |
|
-
|
A set of dynamic correlation keys between aggregated views and data |
|
|
|
What are the benefits in using QueryObject as Data
management Infrastructure? |
|
-
|
Compression |
|
-
|
Speed of generation |
|
-
|
Scalability |
|
-
|
High Performance Access |
|
-
|
Simple, low cost, and comprehensive analitycs and reporting |
|
-
|
Openness to any type of Data Source (Internet, emebedded systems and database); |
|
-
|
Open access from any type of commercial reporting and analytics tools; |
|
-
|
Open access from XML, SOAP, ODBC, JDBC, etc; |
|
-
|
Platform portability, access from mobile devices; |
| . |
| What
kind of application can be developed with QueryObject? |
| QueryObject has been successfully applied for: |
|
| Data
Integration solutions: |
|
Pre/Post Aggregation Processing |
|
High Volume Log, streams, data Movement |
|
Complex ETL architectures. |
|
Data Warehouse & Business Intelligence: |
|
Extreme BI projects; |
| |
DW Appliances Solutions; |
|
Self Service BI; |
| |
Infrastructures and Frontend tools
Performances crisis lifeguard; |
|
Data Services. |
| . |
SaaS BI; |
| |
Application conversion and Business Integration; |
| |
|
|
|
|
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. |
|
|
|
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. |