# Scope of properties

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

- system-wide

  Most properties can be set on a system-wide basis; that is, you set a property for the entire system and all its databases and conglomerates, if this is applicable. Some properties, such as error handling and automatic booting, can be configured only in this way, since they apply to the entire system. (For information about the Derby system, see the Derby Developer's Guide.)

  When you change these properties, they affect any tables or indexes created after this change.

- database-wide

  Some properties can also be set on a database-wide basis. That is, the property is true for the selected database only and not for the other databases in the system unless it is set individually within each of them.

  When you change these properties, they affect any tables or indexes created after this change.

- conglomerate-specific

  Beginning with Derby properties relating to conglomerates cannot be specified as part of the create-statement for the object. These properties (for example, derby.storage.pageSize) must be set at the database level prior to executing the create-statement. These storage-related properties take effect when you create a table or index, and cannot be changed during the lifetime of the conglomerate

Parent topic: Properties overview
Related concepts
Persistence of properties
Precedence of properties
Dynamic versus static properties