Cracking the Vault

Improving SQL Merge Replication Performance in Connected Workgroup Environments.

In a SQL Replicated environment (Connected Workgroups) it is necessary to run regular SQL Maintenance plans on each site to keep the database healthy and optimized for performance. This should be done from one Vault Server in each workgroup. Autodesk has observed significant performance benefits specifically in the merge replication by using the ADMS Console defragmenting tool immediately prior to running a SQL maintenance plan.

The ADMS Console defragment command can be run via

A) the User Interface

B) a windows CMD line by running a batch command as follows:-

Connectivity.ADMSConsole.exe -Odefragmentvault –NVaultDB -VUAdministrator -VPadmin -S

Connectivity.ADMSConsole.exe -Odefragmentlibrary –NCustom_Library -VUAdministrator -VPadmin –S

(If you run a custom SQL Maintenance Plan you can the above lines before or after your existing defragmenting batch scripts.)

If the command is run via the User Interface or without the –S switch, the following message will appear requiring user input

“This operation cannot be performed if the vault is unlocked and available to users. Would you like to lock this vault now? Selecting ‘No’ will abort the operation.”

This message will remain on the screen until Yes or No is clicked. Similarly if you run the command whilst the ADMSConsole is open you will see this message.

Run the ADMS Console defragmentation to see how long it takes. It will vary from one time to another dependent on user activity since the previous ADMS Console defragmentation. One example may be… if it takes 1 hour to process an ADMS Console defragmentation on all databases, double it, then use that time to schedule it before running the SQL Maintenance plan.

An example could be, the following.

The Administrator responsible for running SQL Maintenance on each database, has configured a SQL Maintenance plan to run at mid-day on each Saturday. Testing has revealed that defragmenting all the Vault and Library databases takes 5 hours. Allowing for fluctuations in user activity, since the previous defragmentation, (in the near future) they choose to run the ADMSConsole defragmentation 10 hours prior to the scheduled SQL Maintenance plan.

	Defrag	SQL Maintenance
1 Vault Site Server in Workgroup1	Run Weekly on Saturday @ 0200	Run Weekly on Saturday @ midday
1 Vault Site Server in Workgroup2	Run Weekly on Saturday @ 0200	Run Weekly on Saturday @ midday
1 Vault Site Server in Workgroup3	Run Weekly on Saturday @ 0200	Run Weekly on Saturday @ midday

Note:

                The ADMS defragmentation only needs to be run from 1 Vault Site server in each Connected Workgroup.

Vault Upgrade Documentation is Now Available

Autodesk has recently released detailed documentation on how to Upgrade Autodesk Vault on the Vault Wiki.

There is also a downloadable version posted at the bottom of the above mentioned page.

#23 Do... Setup Database Mail In A Connected Workgroup Environment

Autodesk have published a Best Practice in the Vault Wiki called "Monitoring SQL Replication"

"It is very important to monitor the replication environment.  SQL Server provides replication alerts and threshold settings that can be monitored and emailed to system administrators if an alert occurs or a threshold has been passed."

Cannot Delete Users From Vault - Rename and Disable Instead

A common request is the ability to delete users from the Vault once they have left the company. Vault, won't allow users to be deleted to retain historical information. Once a user has left the company the user can be disabled from within the User Management control within the Vault client itself or the ADMS Console. This prevents the user from accessing any Vault database.

A concern in larger implementations is that the User Management grid will become long and unmanageable.

One suggestion would be to

1. Untick the "Enable user"
2. Edit the User Name to be preceded by "zzz_"
3. Click OK
4. Click the User Name column header to sort Ascending Alphabetically.

 

 

#22 Do... Run A B2BMigrate after Importing a Configuration

In the ADMS Console, you can Export and Import Configurations from other Vault Databases.

 

For more information on Importing and Exporting Configurations, please refer to the Vault Wiki.

More Information on the types of information that is included in the Configuration File can be found here "Secrets of the Vault Configuration File" 

The Best Practice is... after importing the configuration file, run a -Ob2bmigrate to ensure that the changes are fully implemented.

If you create a new Vault database using a configuration file, it should not be necessary to run a -Ob2bmigrate.

#21 Do... Use one Vault Project file (Inventor).

Using multiple Inventor project files can have an impact on how an assembly file resolves the children it consumes. Autodesk has published a best practice on how to configure one Vaulted project file here.

BEST PRACTICE FOR VAULT PROJECTS

 

You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.

#20 Do... Submit any Customer Error Reports to Autodesk.

No one likes to see them. They normally happen at the most incandescently infuriating time and indeed Software vendors don't like to admit that software can sometimes be...slightly less than perfect. Crashes are a fact of life and the reality is that no software is ever perfect. When you experience a crash you are normally, ungracefully dumped back to the desktop, resulting in one of these....

DONT FORGET TO ENTER YOUR EMAIL ADDRESS

All Autodesk software users acknowledge that software is not perfect by accepting the End User License Agreeement (I know you probably never read it :-) ).

However, Error Reports are a fundamental basic tool to allow all software developers to improve the quality of their products. Not only do they provide precise information as to what commands were executed and failed immediately prior to the crash, but they provide invaluable statistical information to development  so they know what issues to fix first based on the numbers submitted. If they get 500 reports from one issue, they will fix that, before addressing the issue reported only 10 times. Simple.

There is a tendency to think that if you send the Error Report, it will disappear into a black hole and the issue will never get fixed. My personal experience is the complete opposite. This is true both of Autodesk products and other vendors like Microsoft. Indeed I have used an erroneous email from home (no way for anyone to tell my name or who I work for) to send an Error Report to Autodesk only to be contacted days afterwards by a QA engineer asking for more information on how to reproduce it. Other times, I have received an email back saying that the issue is fixed in a public hotfix or service pack.

So, if you experience one of the above error reports, and it occurs regularly, it really is in everyones best interests to click "Send Report" every single time.

 

You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.

#19 Do... Enable CIP (Customer Involvement Program).

This enables Autodesk to understand the features of Vault that are most commonly used and to build new functionality in to them. The first time that you run either a Vault Server or Client application you would be asked if you want to participate. If you clicked OK to the default option “No, Thanks”, you can re-enable it from the Help Pulldown menu.

 

You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.

#18 Do... Participate in the next release Vault Beta program.

Currently, Autodesk releases new versions of Vault on an annual basis. The software evolves from one release to the next. The most effective mechanism that Autodesk has to ensure that the software is released with as many issues as possible addressed before it is release is for customers to test the new functionality and migration processes with copies of their production databases. Typically, next release beta programs run between December and Spring and are announced on the official Autodesk public discussion forums.

 

You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.

#17 Do... Understand what language combinations are supported for Vault.

Vault Server and Client software is supported in a limited number of language configurations. These are documented in TS1093327.

 

You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.