DB2® Everyplace® and Apache Derby are similar, but have features that might make one a better choice for client needs.
Table 1. DB2 Everyplace and Apache Derby comparison
|DB2 Everyplace||Apache Derby|
|Implementation Type ||High performance native implementation (see DB2E documentation for a complete list of supported devices) ||Java-based (platform independent) implementation |
|On-Disk Footprint ||250 KB ||2 MB |
|Number of connections supported ||Allows multiple concurrent connections to a database from the same VM||Allows multiple concurrent connections to a database |
|SQL Support ||Limited set of SQL data types ||Full SQL-92 support, partial SQL-99 support |
|Schema Support ||No||Yes |
|Database Creation Requirements ||Directory for database tables must be created prior to use ||Apache Derby creates directory |
|JDBC URL ||jdbc:db2e:location|
If no database exists at the location, a new database structure is created
Database creation requires the addition of an explicit create=true attribute to the URL
In addition, the database location can also refer to a zip or JAR file in the case of a read-only database
|Lifecycle management provider available||No||Yes|
Refer to the product documentation for more complete information about these products.
Parent topic: Databases: XPD621