Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
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
We had this issue with my client. For the IT people is easier manage in some cases a default instance name, because the SQL server can administrate processors and memory more efficiently. This behavior must be an option in the Vault installation process.
I see that this request was accepted 6/2015. Has any progress been made on implementing it? I don't see this change in Vault 2018.
As an additional note, for users that use Vault with SQL Express, this may not be such a big deal. For larger, more extensive Vaults, we use a separate server running full SQL Server.
We have a separate dev environment that is running a mirror image of our production Vault.
When evaluating a new release, such as Vault 2018, I don't want to wreck my existing dev environment that is still running Vault 2016 or Vault 2017. I want to be able to set up another Vault server with Vault 2018 and go through the process of migrating the Vault, etc. while still having the original Vault to fall back on.
Our SQL Server can easily handle 10s or even 100s of different instances.
But because the instance name is hardcoded to AUTODESKVAULT, I cannot have my Vault 2016 and Vault 2018 use that same SQL Server.
I'm now forced to either just use SQL Express for the new version, which isn't ideal and doesn't let me truly test with the same hardware or setup, or fork out a lot of money for another SQL Server license that I can put on a new server just because Vault won't let me specify a different name for my Vault instances.
We are a large corporation with a dedicated DB department. There are naming conventions that must be kept for SOX and Company standards. It is a must have to be able to name my external DB instance. SQL Express is not our standard and must be moved to the full SPL implementation. Our DB will soon be to big for express was well. This needs to change or we will be forced to go with a different PDM. This will need to happen soon before we expand Autodesk Vault to North America. Please resolve ASAP. Hardcoding variables is so 1990.
The lack of this very basic feature has forced us to abandon all future plans for Autodesk Vault. The requirement to manage separate SQL servers for every Vault version and test instance, and the expensive SQL licensing that goes along with it, is irresponsible to demand from customers. We're switching platforms and will not be renewing in 2020. It's a pity that the Vault team was unable to resolve such a simple issue since it was first brought to light seven years ago.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")