In Brief, EVOLUTION is a data management
technology that works WITHIN industry-standard relational database
engines such as Oracle, DB2 and MSSQL. EVOLUTION gives these RDBMS
engines the ability to work with a dynamic, object data model that
remains flexible throughout any applications lifespan.
2. Can EVOLUTION work with existing applications?
Software developers have the option to adapt
existing applications to use EVOLUTION for all data access requirements,
and/or to create new applications that can interface with the existing
3. What are the space requirements?
EVOLUTION requires LESS space than traditional,
hand-coded data models. EVOLUTION has an exceptionally efficient
data storage algorithm. For example, EVOLUTION does not store redundant
information, nor does it take any space for empty or null fields.
4. Is EVOLUTION used for development or
for continuous work?
Both. You can develop your application very
rapidly using EVOLUTION, and once the application is deployed, you
can continue to work and make changes with the same flexibility
and speed, even when the system is live.
5. What is the advantage of coding data
access using EVOLUTION (rather than making a query directly to the
Easier, quicker, and far more flexible. By
taking advantage of EVOLUTIONs built-in Adaptive Data Architecture,
data structure limitations and bottlenecks are a thing of the past.
6. What is the difference between SQL
queries and Evolution calls?
EVOLUTION calls are much easier to learn,
code, modify, and maintain. SQL queries are hard-coded to the specific
database that they are written to access. EVOLUTION calls are both
database and application independent (so developers use the same
calls regardless of the RDBMS or application being developed).
7. Who writes the access procedures?
With EVOLUTION, developers no longer code
data access procedures. Access procedures are transparently handled
on the fly by EVOLUTIONs highly optimized algorithms.
8. If there is an existing application,
what is the process to migrate to EVOLUTION?
Step 1. Create an appropriate (empty) data
model using EVOLUTION
Step 2. Replace all database calls with EVOLUTION calls in your
Step 3. Migrate your existing data into the new data model
9. When flexibility is that easy, how
will we make sure no one can go in and damage the data structure?
Evolution has very strict administrative
controls. The database administrator decides who will have access/permission
to view (or to make changes to) the data structure.
10. Can a traditional table structure (schema)
be exported from EVOLUTION ?
Yes, if you really want to, you can export
conventional tables. However, you will thereby "freeze"
your data model into a rigid form, and it will no longer be able
to change or adapt on the fly.
To find out how EVOLUTION can help you
develop a more flexible software solution in less time, email SYGENICS
at or call (514) 862-5514.