I have an up and running Vault Professional 2013 instance on a single server with SQL 2008 R2.
I want to leave ADMS on that server and just change the SQL instance to a different server to increase performance as described in some autodesk vault articles.
I see how to do this within a new setup during the setup dialog by configuring remote sql.
How can I do this with an already installed system?
Steps (to be edited by someone who knows how to do it):
1.) Turn on TCP/IP protocol and sql browser on the new sql server
2.) Backing up KnowledgeVaultMaster and Vault database and restoring on the new server
3.) What about sql logins / windows logins on the new sql server and existing adms server?
4.) How to tell the ADMS to connect to the new sql server?
Thx for your help,
Try these steps:
everything perfect until step 7.
I am able to start ADMS Console. The console succesfully points to the new SQL server (if i try to attach an existing database the selection dialog points to the new server).
The problem now is, that there seems to be a rights problem with the new sql server. i get a sql error (error in converting system.dbnull to string) that is a problem with sql user rights when i try to create a new knowledge vault master.
could you please describe which users/schemas/roles i have to create on the new sql server (AUTODESKVAULT instance exists, but no autodesk console installation; so no VaultSys SQL user,...) to make this work?
I tried to manually create the VaultSys sql but did not make it good enough to work.
I did exactly what was described there:
- Create sa
- Create VaultSys
incuding the necessary credentials/roles
The problem still persists.
Error says "Object of type "system.dbnull" cannot be converted to type "system.string". when trying to create a new KVM. If i attach the KVM with SQL Studio the error message appears when starting the adms console.
When you install SQL on the other server, what collation did you select? If that fails, I would recommend that you uninstall the Vault Server and reinstall it and point to the remote server. You will have to uninstall the local SQL instance for the installer to enable you to point to the remote server.
Collation is in fact different! Although both SQL installations were installed with default settings for the collation the existing says "Latin_1_General_CI_AS" and the new one says "SQL_Latin_1_General_CP1_CI_AS".
Don´t know if the code page and the beginning "sql" makes a difference but i will install the instance new with the exact same collation.
thx, i will give feedback,
Actually I believe those 2 collations are the same. Microsoft changed the names in newer versions of SQL.
I would go with my other recommendation of re-installing Vault server and let the setup configure SQL for you.
Don´t know what helped here, but after I reinstalled the SQL instance and defined the collation to be exactly Latin_1_General_CI_AS and additionally reinstalled adms console everything works now!
Thanks for your inputs and help!
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.