Shuts down the specified database if you specify a databaseName. (Reconnecting to the database reboots the database.) For a database for which authentication and SQL authorization are both enabled, only the database owner can perform shutdown of that database. Please see "Enabling user authentication" and "Setting the SQL standard authorization mode" in the Java DB Developer's Guide for more information.
Shuts down the entire Derby system if and only if you do not specify a databaseName.
When you are shutting down a single database, it lets Derby perform a final checkpoint on the database.
When you are shutting down a system, it lets Derby perform a final checkpoint on all system databases, deregister the JDBC driver, and shut down within the JVM before the JVM exits. A successful shutdown always results in an SQLException indicating that Derby has shut down and that there is no connection. Once Derby is shut down, you can restart it by reloading the driver. For details on restarting Derby, see "Shutting down the system" in the Java DB Developer's Guide.
Checkpointing means writing all data and transaction information to disk so that no recovery needs to be performed at the next connection.
This attribute may be combined with the deregister=true attribute.
When you shut down a database, if authentication is turned on, you must specify this attribute in conjunction with the user=userName and password=userPassword attributes. If both authentication and SQL authorization are turned on, the user must be the database owner.
When you shut down the Derby system, if both authentication and SQL authorization are turned on, you must specify this attribute in conjunction with the user=userName and password=userPassword attributes.
-- shut down entire system jdbc:derby:;shutdown=true -- shut down salesDB (authentication not enabled) jdbc:derby:salesDB;shutdown=true -- shut down an in-memory database using the embedded driver jdbc:derby:memory:myInMemDB;shutdown=true -- shut down an in-memory database using the Network Server jdbc:derby://localhost:1527/memory:myInMemDB;shutdown=true