Configure Derby to use an in-memory database

If you use Derby's in-memory database facility, it is important to configure the following:

If you want to prevent Derby from writing anything to the derby.log file, use one of the properties (for instance,

For more information, see "Using in-memory databases" in the Derby Developer's Guide.

Related concepts
Use prepared statements with substitution parameters
Create indexes, and make sure they are being used
Ensure table statistics are accurate
Increase the size of the data page cache
Tune the size of database pages
Avoid expensive queries
Use the appropriate getXXX and setXXX methods for the type
Tune database booting/class loading
Avoid inserts in autocommit mode if possible
Improve the performance of table functions
Increase the concurrency of sequences