# Generating the DDL for a database

The `dblook` utility generates all of the following objects when generating the DDL for a database:

- Checks
- Functions
- Indexes
- Jar files
- Keys (primary, foreign, and unique)
- Schemas
- Stored procedures
- Triggers
- Tables
- Views
- Roles

Note: When dblook runs against a database that has jar files installed, it will create a new directory, called `DERBYJARS`, within the current directory, and that is where it will keep copies of all of the jars it encounters. In order to run the generated DDL as a script, this `DERBYJARS` directory must either 1) exist within the directory in which it was created, or 2) be moved manually to another directory, in which case the path in the generated DDL file must be manually changed to reflect to the new location.

The `dblook` utility ignores any objects that have system schemas (for example, SYS, SYSIBM), since DDL is not able to directly create nor modify system objects.

Parent topic: dblook
Related concepts
Using dblook
Related reference
dblook options
dblook examples