---
title: "Custom loading procedures"
canonical: "https://docs.vaultspeed.com/space/VPD/3081699382/Custom%20loading%20procedures"
format: markdown
---
This article is only relevant if u don't use our FMC application which manages this all.

## Initial load Source / Data Vault

1. Insert a record in the SCHEMA_MTD.LOAD_CYCLE_INFO_TABLE_NAME table with:
  1. Load cycle id: the unique number of the load, this sequence is independent of the source.
  2. Load date (if single load cycle parameter is enabled): the start time of the load.
2. Execute EXT loads. (all these mappings can be executed in parallel)
3. Execute STG loads. (all these mappings can be executed in parallel)
4. Execute FL loads. (all these mappings can be executed in parallel)
5. Calculate the indices on the FL tables.

## Incremental load

First the parameters of the load have to be determined/chosen, these values have to be entered in the corresponding metadata tables but since those tables can only contain a single record and are not persisted between delta generation deployments, we recommend logging these values somewhere else (a metrics vault), together with other information like loading times, error logs, etc.

1. Truncate and Insert a record in the SCHEMA_MTD.LOAD_CYCLE_INFO_TABLE_NAME table with:
  1. Load cycle id: the unique number of the load, this sequence is independent of the source.
  2. Load date (if single load cycle parameter is enabled): the start time of the load.
2. Truncate and Insert a record in the SCHEMA_MTD.FMC_LOADING_WINDOW_TABLE_NAME table with:
  1. FMC_BEGIN_LW_TIMESTAMP: start of the loading window
    FMC_END_LW_TIMESTAMP: end of the loading window. All the changes with modification/CDC timestamp between the start and end of the window will be loaded.
3. Execute DFT loads (if persist delta firewall parameter is on, otherwise only views are used). (all these mappings can be executed in parallel)
4. Execute EXT loads. (all these mappings can be executed in parallel)
5. Execute STG loads. (all these mappings can be executed in parallel)
6. Execute FL loads. (all these mappings can be executed in parallel)
7. Recalculate the indices on the FL tables.

## Business Vault load

the load parameter tables can all be found in the PROJECT_FMC schema as supposed to the SOURCE_MTD schemas.

1. fill in the bv loading window table (this is used for loading the PIT tables).
2. fill in the bv_load_cycle_info table with the load cycle id and load date for the bv load.
3. in the dv_load_cycle_info table, add all the load cycle id's of the DV loads since the last BV load (this will be used to determine which records need to be loaded in the links across sources).
4. run all BV mappings (in parallel).
5. analyze the BV tables.

> ℹ️ The load metadata tables of VaultSpeed can not be used to store persistent data, since they can be cleared as part of the release process!