Products

Elevate Software develops, markets, and sells both database engine products (ElevateDB and DBISAM) and a web application development product (Elevate Web Builder).

Our first-generation database engine product, DBISAM, is a good fit for Delphi and C++Builder application developers wanting a fast and highly-customizable database engine that compiles directly into their applications, especially when replacing the BDE (Borland Database Engine) in existing applications.

Our next-generation database engine product, ElevateDB, is geared toward all database application developers, and is available for almost all development environments.

Our latest product, Elevate Web Builder, is a development environment for building web applications that rival desktop applications in terms of performance and functionality. It is an excellent fit for the desktop application developer that wants to rapidly develop applications for the web without the traditional long learning curve associated with web application development.

Product Information

Use the following links to access the specific information for a product.

Access the ElevateDB product information	Access the DBISAM product information
Access the Elevate Web Builder product information

Database Engine Product Comparison

We want to make sure that you select the database engine product that is right for your needs. The ElevateDB and DBISAM products are similar in some respects but very different in other respects. We have provided the following feature comparison chart to help detail the similarities and differences between the two products.

DBISAM

ElevateDB

Access Methods
Direct-access (single or multi-user, file-sharing)
Client-server access (LAN or Internet/WAN)
SQL access
Direct table access
Administration
Remote server administration
Activity logging [1]
Text import and export
Scheduled server jobs
Compilation Support
Compiles directly into executable (if supported by development environment)
Compilable as .NET managed code
Source code available
Customizations
Engine signature support [2]
File names and extensions
Custom encryption
Custom compression
Custom memory buffer settings
Large file support (greater than 4GB files)
Direct Table Access
Row navigation (first, last, next, prior, move by)
SQL expression and callback filters
Ordering by a specific index
Searching by a specific index key
Index key ranges
Accurate row counts with expression filters and index key ranges
Logical row numbering
Disaster Recovery
Online backup and restore
Table repair
External Access
ODBC driver
ADO.NET data provider
General features
In-memory databases [3]
Multi-threading support
Replication
Table versioning
Table encryption [4]
Long table, column, constraint, and index names with descriptions [5]
Configurable table index page and BLOB block sizes
Index key compression [6]
BLOB column compression
Native code procedures and functions [7]
Internationalization
Unicode support
Table-level collations
Column-level collations
Collation-specific case-insensitivity
Collation-specific accent-insensitivity
Collation-specific Kana and width-insensitivity
SQL COLLATE clause for definition and casting
Different collations for base columns and indexed columns
Performance
SQL query and filter optimizer
Query execution plans
Remote Sessions
Encrypted connections
Adjustable data compression
Pinging support to keep idle connections alive
Connection activity tracing
Connection send/receive progress tracking
Bi-directional client-side cursor caching
SQL Support
SQL-92 support
SQL-2003 support
NULL support [8]
Query expressions as values
Database catalogs
Information schema tables
Views
Triggers
Primary key constraints [9]
Unique key constraints [10]
Foreign-key constraints
Check constraints [11]
Column defaults [12]
Required (not nullable) columns
Generated columns
Computed columns
Identity (auto-increment) columns [13]
BLOB columns
Stored procedures
Functions
Derived tables
Cursor support in stored procedures, functions, triggers, and scripts
EXISTS operator
Date/time interval support
Optimized LIKE searches with leading wildcards
Row Value Constructors
SQL/PSM Support
Cursors and fetching
Branching (IF, CASE)
Looping (WHILE, LOOP, REPEAT)
Variables (DECLARE)
Dynamic SQL support (PREPARE, EXECUTE)
DDL support (CREATE, ALTER, DROP)
Code blocks (BEGIN, END)
Exception handling (BEGIN, EXCEPTION, FINALLY, END)
Logging, status and progress tracking
ARRAY support
Server
Runs as a Windows service
Multi-threaded
White and black lists by IP address for incoming connections
Licensed session/connection configuration
Configurable connection timeouts
Configurable connection cleanup for orphaned connections
I/O statistics and session locking information
Text Indexing
Customizable text filtering [14]
Customizable word generation
Customizable word filtering
SQL support for searching/filtering using text indexes
Optimized searches with trailing wildcards
Optimized searches with leading wildcards
Transactions and Locking
Serialized transactions
Transactions on a specific table or set of tables
Pessimistic row locking
Optimistic row locking
Manual cursor row locking
Row change detection and notification [15]
User Security
SQL standard users, roles, and privileges
Server security
Database privileges
Table privileges
Procedure privileges
Function privileges
View privileges
Utilities
Interactive utility for general database management
Interactive utility for migrating data from other formats [16]
Interactive utility for server administration [17]

[1] DBISAM only provides logging for the DBISAM Database Server, while ElevateDB provides logging for all database access
[2] Allows a developer to only allow access by the developer-defined engine signature
[3] DBISAM only allows one system-defined "Memory" in-memory database, while ElevateDB allows for multiple user-defined in-memory databases
[4] The table encryption in DBISAM is performed using a developer-defined password for each table, while ElevateDB uses one engine-level password for all tables
[5] ElevateDB provides for long identifiers and descriptions for all database objects, including stored procedures, functions, triggers,and views.
[6] The index key compression must be specified by the developer in DBISAM, while ElevateDB performs index key compression automatically
[7] ElevateDB requires that all native code procedures be compiled as DLLs that are loaded on-demand, whereas DBISAM procedures are compiled directly into the application or server
[8] DBISAM is non-standard - empty CHAR/VARCHAR and CLOB (memo) columns are treated the same as NULL
[9] DBISAM is non-standard - primary keys can be NULL
[10] DBISAM is non-standard - unique keys do not allow duplicate NULL keys
[11] DBISAM is non-standard - only simple minimum and maximum column values and no table-based check constraints
[12] DBISAM is non-standard - only simple default values and no expressions
[13] DBISAM is non-standard - cannot specify seed value and/or increment value
[14] DBISAM can only filter text based upon the index column text, while the filtering in ElevateDB can be performed based upon the contents of a separate "type" column
[15] Notification is mandatory in DBISAM while in ElevateDB it can be turned on and off
[16] DBISAM provides this functionality via a separate utility, while ElevateDB provides this functionality within the database manager
[17] DBISAM provides this functionality via a separate utility, while ElevateDB provides this functionality within the database manager

Royalty-Free Licensing

Elevate Software licenses its database engine products for royalty-free use with your compiled and distributed applications. You are only required to buy a single license for each licensed copy of the development environment that you use to build your application along with the Elevate Software database engine product.

All applications created using Elevate Software web application development products can be distributed royalty-free. You are only required to buy a single license for each developer that is using the product to create and/or compile any web application.