Ancelus

No compromise

Relational database designers usually build table structures to optimize for data entry or data retrieval. Only in rare — and simple — cases is it possible to optimize for both. Ancelus is always tuned and supports high data input rates and high retrieval performance concurrently. Even with completely random storage, Ancelus never looks at uninteresting data.

Next »

No tuning

In Ancelus, design efficiency is improved by directly mapping the threaded network of the ERD to the database. The tables — and their names — are created as a “virtual view” of the threaded network with no involvement from the developer.

Since the Ancelus structure is a direct mapping of the ERD, there is no re-design required to “tune” the system.

Next » « Previous

No normalization

Through using virtual tables, database normalization is a thing of the past. The table definition step in database design is replaced with a direct mapping of the entity-relation diagram. The design process goes from entity-relation diagram to fully optimized and functional live database in minutes.

No art required, only typing (or fill in the blanks in the control panel, if you prefer).

Next » « Previous

No duplication

Duplication of data is never required. Changing the data entry in one location changes it throughout the database by reference — instantly. No more downtime for updates. Data entry is visible and functional in the database in 10s of nanoseconds.

Storage on disk is a background task and may be delayed up to several hundred milliseconds.

Next » « Previous

No waiting

Long waits for administration runs, disk defragmentation functions, and maintenance activities are relics of the past. A Dynamic Data Dictionary that supports real-time (less than one second) revisions to a live database allows true rapid prototyping and eliminates maintenance downtime in a deployed application.

Don’t give DBAs an excuse to complain about your slow database! Talk to us today.

« Previous