Allow Vault installation/configuration to connect to an Instance not named AUTODESKVAULT
We have several separate vault servers (Professional) all connected to remate databases on an SQL cluster. The SQL people claim that they can only have one single instance called AUTODESKVAULT in their complete environment AND that instance names MUST follow their naming conventions
Actually, vault is the only software that I know of that requires a specific instance name
There should be a relatively simple option in ADMS to truncate data from the vault, or to backup just the configuration.
Doing an implementation at a publicly traded company means going to a multi-stage process (dev, test, UAT, Prod) with multiple vault environments to verify the configuration before go-live. It would be very convenient to be able to either remove all of the files from the vault to provide a clean starting point for a new environment.
Alternately, the option to backup JUST the configuration would be a huge help as well.