A Vault implementation can be as simple as installing all components on a single computer, or as complex as installing components
on several computers in different locations. The more complex the Implementation, the more information there is to consider.
The following sections outline information to consider to make the best decisions for your Vault implementation.
Number of Users
Knowing the number of users helps prevent access problems and slow response times. For example, if you have more then ten
concurrent users, use Windows® Server 2003 or 2008. For more than 25 users, consider upgrading to the full standard edition
or enterprise edition of SQL. Microsoft SQL Express allows only 25 concurrent connections. When implementing Vaultfor a single user, you can load all the components on a single computer.
Number of Servers
When determining the number of servers, keep in mind how information flows from the client computer to the Vault server to the SQL server and back. (See How Vault Works for more information.)
Server Hardware Specifications
For the recommended and preferred system requirements, refer to the Installation Requirements section in this topic. Vault is more processor intensive than memory intensive like some other applications. Avoid loading Vault components on servers that already have a high CPU usage.
Server Operating Systems
Vault Server can be loaded on several different operating systems. When deciding to use a non-server operating system, consider
the limitations.
For example:
- Windows 7 has a limit of ten concurrent users and three concurrent web service requests.
Firewalls
Firewalls can block incoming requests. During the Vault Server installation, the server is checked for known firewalls. Firewalls can require that you configure them to allow the
Vault Server to communicate correctly. Some system protection software can include firewalls. Check these tools for the existence
of firewalls.
Applications on Servers
Vault can be processor intensive. Loading the Vault Server on a server with other processor intensive applications can cause Vault to run slower than expected.
Microsoft SQL Version
Autodesk Vault requires a minimum of Microsoft SQL 2008 Express service pack 3. If necessary, upgrade your previous version of Vault with
2008 Express to service pack 2. See the Installation Requirements section in this topic for more information.
Autodesk Vault 2014 requires a minimum of Microsoft SQL 2008 Express service pack 2. If necessary, upgrade your previous version
of Vault with 2008 Express to service pack 2. See the Installation Requirements section in this topic for more information.
SQL 2008 Express has a limitation of 25 concurrent users and a 4-GB size restriction. If your Vault implementation requires more capacity, set up the Vault server using the Standard or Enterprise versions of SQL.
Additionally, Vault 2014 supports SQL Server 2008 R2 Express, which increases the single database size restriction to 10-GB.
Access Frequency
How often the Vault Server is accessed affects the server performance. For example, a Vault implementation with 50 users and one or two users checking out one or two files a day does not tax the server much. Using
the same configuration with 35 of the users accessing the vault every 10 minutes, Vault Server performance differs, running at the non-recommended requirements.
Network Speed
Although network speed is commonly equated to latency, you should also consider bandwidth and throughput. Network speed is
an important factor to consider when trying to get the best performance for your Vault implementation. By running tests to measure your latency, bandwidth, and throughput between all of the servers, you can gain
an idea of how fast the connections are. Copy a few large files from one server to another. When performing this test, copy
from Server A to Server B and then copy from server B to Server A. Data traveling from one server to another does not always
take the same route when traveling back.
Additional Considerations for Distributed Teams
If you are installing the server components for Vault Professional, you have several options to better support teams distributed across multiple locations. Vault Professional supports Multi-Site replication with a central remote database. Vault Professional also allows a single site to implement Vault with a dedicated database server.
Multi-Site
Multiple remote sites can be configured to access the same vault data. A site is comprised of a dedicated Autodesk data management
server and a file store. Each site accesses a shared AUTODESKVAULT SQL instance.
Replication
Replication is the process of copying data from one server to another server usually located in two different physical locations.
This process allows the setup of a Vault environment which has two different locations and users will not have to spend time downloading large CAD files across their
Wide Area Network (WAN) connection.
The connected workgroup feature in Autodesk Vault Professional supports the use of multiple database servers using Microsoft SQL Publisher/Subscriber technology. This technology
allows the replication of the SQL database at multiple locations.
