2011

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
Vault 2011 requires a minimum of Microsoft SQL 2005 Express service pack
3. If necessary, upgrade your previous version of Vault with 2005 Express to
service pack 3. See
Installation Requirements on page 12.
SQL 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.
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 users accessing the vault every 10 minutes, Vault
Server performance differs, running at the non-recommended requirements.
Network Speed
All though network speed is commonly equated to latency, you also consider
bandwidth and throughput. Network speed is an important factor to consider,
when trying to get the best performance for your Vault implementation.
Without running tests to measure your latency, bandwidth, and throughput
between all 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.
Applications on Servers | 21