Description: You can improve the performance of update-intensive, large databases by putting a database's log on a separate device, which reduces I/O contention.
Keywords: Logging transactions, Transaction log, putting on separate device, Log, default location for

# Logging on a separate device

You can improve the performance of update-intensive, large databases by putting a database's log on a separate device, which reduces I/O contention.

By default, the transaction log is in the log subdirectory of the database directory. Use either of the following methods to store this log subdirectory in another location:

- Specify the non-default location by using the logDevice attribute on the database connection URL when you create the database.
- If the database is already created, move the log manually and update the service.properties file.

- Using the logDevice attribute
  To specify a non-default location for the log directory, set the logDevice attribute on the database connection URL when you create the database.
- Example of creating a log in a non-default location
- Example of moving a log manually
- Issues for logging in a non-default location

Parent topic: Part two: Derby Administration Guide
Related concepts
Checking database consistency
Backing up and restoring databases
Obtaining locking information
Reclaiming unused space