You can also configure your system to automatically boot all databases
in the system when it starts up; see derby.system.bootAll in the manual. Because of the time needed
to boot a database, the number of databases in the system directory affects
startup performance if you use that configuration.
Once a database has been booted within a system,
it remains active until the system
has been shut down or until you shut down the database individually.
When boots a database,
a message is added to the error log. The message includes the version
that the database was booted with, for example:
2006-10-04 03:54:06.196 GMT: Booting version
- 10.2.1.5 - (448900): instance c013800d-00fd-0cb0-e736-ffffd1025a25 on
database directory sample
The number of databases running in a system
is limited only by the amount of memory available in the JVM.