# System procedures for storing jar files in a database

`SQLJ.INSTALL_JAR`, `SQLJ.REMOVE_JAR`, and `SQLJ.REPLACE_JAR` are a set of procedures in the SQLJ schema that allow you to store jar files in a database.

Your jar file has two names:

- A physical name (the name you gave it when you created it)
- A Derby name (the Derby identifier you give it when you load it into a particular schema). The Derby name, an SQLIdentifier, can be delimited and must be unique within a schema.

A single schema can store more than one jar file.

For more information on when and how to use these procedures, see "Loading classes from a database" in the Derby Developer's Guide.

- SQLJ.INSTALL_JAR system procedure
  The SQLJ.INSTALL_JAR system procedure stores a jar file in a database.
- SQLJ.REMOVE_JAR system procedure
  The SQLJ.REMOVE_JAR system procedure removes a jar file from a database.
- SQLJ.REPLACE_JAR system procedure
  The SQLJ.REPLACE_JAR system procedure replaces a jar file in a database.

Parent topic: Built-in system procedures