--- title: Database Utility category: reference order: 99 --- `Database Utility` is a tool for managing database entries created by abapGit. You can access the tool via the tools icon in the top right corner of the abapGit home page [](img/utilities.png). It's possible to edit database entries of type - `SETTINGS` - `USER` - `REPO` - `BACKGROUND` Caution: Backup all abapGit database entries, first! Be careful when you edit these entries from within abapGit. Corrupting the XML or setting invalid options might break your abapGit! ![](img/db_util_1.png) ![](img/db_util_2.png) ## Global Settings The `SETTINGS` entries contain global (not user-specific) settings for your abapGit installation. This is an example: ```xml myproxy.com 8080 X I dont.use.proxy.com 50 Update $OBJECT 72 ``` ## User Settings A `USER` entry contains meta information like the favorites of an user and their repository configurations e. g. name and email address for Git. This is an example of a `USER` entry: ```xml 000000000001 000000000002 000000000003 https://[...]/file.git my_username First and Last Name email@example.com https://[...]/file.git my_second_user First and Last Name email@example.com 0 ``` ## Repository Meta Data The `REPO` entries contain meta data like Git repository URL, branch and package information and information about files known and to be excluded. This is an example: ```xml https://[...]/file.git refs/heads/my_branch Z_MY_PACKAGE my_user 20200418201549.200418 my_user 20200507134505.184445 / .abapgit.xml [...] DEVC Z_MY_PACKAGE Z_MY_PACKAGE /src/ package.devc.xml [...] DEVC Z_ANOTHER_PACKAGE Z_ANOTHER_PACKAGE /src/abaplinted_sample/ package.devc.xml [...] PROG Z_MY_REPORT Z_ANOTHER_PACKAGE /src/abaplinted_sample/ z_my_report.prog.abap [...] /src/abaplinted_sample/ z_my_report.prog.xml [...] E /src/ PREFIX /.gitignore /LICENSE /README.md /package.json /.travis.yml /.gitlab-ci.yml /abaplint.json /azure-pipelines.yml /src/.gitkeep My Test Repository ZMY_CHECK_VARIANT X ``` If you remove a repository entry from the database util, the repository is not shown in abapGit anymore. This is useful for example if you want to remove a repository which has a non-existing package assigned and thus can't be opened and deleted normally. ## Background The `BACKGROUND` entries show the method and the repository key for which the background action will be executed: ![](img/background_6.png) The respective XML file contains the method and optionally the credentials needed for a push: ```xml ZCL_ABAPGIT_BACKGROUND_PULL ``` ## Backup & Restore You can backup the abapGit database entries using the menu. Entries are stored in a separate XML-file and combined into a single ZIP-archive named `abapGit_Backup__