The vLCM service maintains its own schema. All changes to it should happen only here.

When there is a new change required, a new folder with the next number should be created.
In it, the Expand and Contract pattern should be followed. Create three files:
- expand.sql -> Expand logic to be run on the source machine.
- contract.sql -> Contract logic to be run on the target machine.
- revert.sql -> Revert of the Expand logic to be run in case of revert on source.

Note, if the change is behind FSS add it in the FSS_PROTECTED_VERSIONS and ensure
that the FSS is populated correctly.

The expand.sql/contract.sql files should follow the given format:

BEGIN;

--Business logic

INSERT INTO UpgradeTracking(ID, Operation) VALUES(:ndu_id, :ndu_operation);
COMMIT;