# Properties overview

Derby lets you configure behavior or attributes of a system, a specific database, or a specific conglomerate (a table or index) through the use of properties.

Examples of behavior or attributes that you can configure are:

- Whether to authorize users
- Page size of tables and indexes
- Where and whether to create an error log
- Which databases in the system to boot

- Scope of properties
  You use properties to configure a Derby system, database, or conglomerate.
- Persistence of properties
  A database-wide property always has persistence. That is, its value is stored in the database.
- Precedence of properties
  The search order for properties is as follows.
- Dynamic versus static properties
  Most properties are dynamic; that means you can set them while Derby is running, and their values change without requiring a reboot of Derby. In some cases, this change takes place immediately; in some cases, it takes place at the next connection.

Parent topic: Working with Derby properties
Related concepts
Setting Derby properties
Properties case study