|
|
|
|
|
|
|
|
Diagram
in PDF format
Above is the CONNX enterprise data model. CONNX has a
distributed SQL engine, meaning that the work of processing
queries is distributed between the client and the server. Most
of the CPU-intensive query processing, such as data conversion
and sorting, is performed on the PC. All of the data retrieval
is performed on the server. In the case of desktop databases,
such as DataFlex or Access, all processing is done on the PC
because there is no server component. The following table
shows the distribution of labor in the CONNX architecture:
This distributed architecture has several advantages:
-
When performing joins, significantly less data is sent
across the network because no duplicates are transmitted.
-
The workload on the data server is minimal, because
CPU-bound tasks are moved to the client, resulting in a
reduction of load on the data server and better
performance across the enterprise.
-
When several users are issuing queries simultaneously,
the CPU power of each client computer is utilized in
addition to that of the server, resulting in true parallel
processing. This makes CONNX highly scalable to a large
enterprise.
|
Client PC
|
Server
|
|
Meta Data Retrieval (CONNX CDD)
|
|
|
First Pass SQL Optimization
|
|
|
Partial Joins
|
|
|
Sorting
|
|
|
Grouping
|
|
|
Extended SQL Functions
|
|
|
CONNX Security
|
|
|
|
Indexed Retrieval
|
|
|
Non-Index Retrieval
|
|
|
Partial Joins
|
|
|
Data Compression (If Requested)
|
|
|
RPCs (Remote Procedure Calls)
|
|
|
Database Security (Client)
|
|
|
|
|
|
|
|
|
|
|
|
|
