Autodesk 46304-050008-1600A Implementation Guide - Page 27

Applications on Servers, Microsoft SQL Version, Access Frequency, Network Speed

Get Autodesk 46304-050008-1600A - Vault R4 Essentials Aotc PDF manuals and user guides
UPC - 606121640691
View all Autodesk 46304-050008-1600A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
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