derby.storage.rowLocking

When you disable row-level locking, you use table-level locking.

Row-level locking uses more system resources but allows greater concurrency, which works better in multi-user systems. Table-level locking works best with single-user applications or read-only applications.

If you use row-level locking (the default), the system decides whether to use table-level locking or row-level locking for each table in each DML statement. In certain situations, the system might choose to escalate the locking scheme from row-level locking to table-level locking to improve performance.

For more information about locking, see "Locking and performance" in Tuning Derby, and "Locking, concurrency, and isolation" in the Derby Developer's Guide.

Default

True.

Example

-- system-wide property
derby.storage.rowLocking=false

-- database-level property
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
    'derby.storage.rowLocking', 'false')

Dynamic or static

This property is static; if you change it while Derby is running, the change does not take effect until you reboot.