Scope of properties

You use properties to configure a Derby system, database, or conglomerate.

For properties that affect conglomerates, changing the value of such properties affects only conglomerates that are created after the change. Conglomerates created earlier are unaffected.

Note: Database-wide properties are stored in the database and are simpler for deployment, in the sense that they follow the database. Database-wide properties are also recommended for security reasons when you use Derby BUILTIN user authentication (see Derby and security). System-wide properties can be more practical during the development process.
Important: Derby's BUILTIN authentication mechanism is suitable only for development and testing purposes, and it will no longer be documented in future releases. It is strongly recommended that production systems rely on NATIVE authentication, an external directory service such as LDAP, or a user-defined class for authentication. It is also strongly recommended that production systems protect network connections with SSL/TLS.
Related concepts
Persistence of properties
Precedence of properties
Dynamic versus static properties