This question occassionally crops up from partners and customers.
The amount of memory needed is often directly linked to the amount of data needed in the cache to achieve high cache hit ratios.
Its not possible to have too much memory for SQL Server, but there must be some left over for the Operating System. So as a general rule of thumb is to have 90% of memory for SQL and leave 10% for the OS to handle general processing.
(The above suggestion assumes that SQL is running on a dedicated server with no other applications such as IIS or another SQL instance is running.)
In some situations it is necessary to limit the numbers of Users connecting to a Vault Server.
This can be achieved in a number of ways, such as using different licence servers for each Vault Server. In this blog article, I am discussing Limiting Web Site Usage by throttling the number of Concurrent Connections.
In Internet Information Services (IIS) Manager, on the Default Web Site, in the Advanced Settings, is an expandable node called "Connection Limits". there is a setting "Maximum Concurrent Connections", which in IIS 7.0, has a default setting of "4294967295". Enforcing a non-default setting requires an IISRESET.
Changing this value will limit the number of connections at anyone time to the Vault Server. When the limit is reached, a user will receive a message like this.
"The request failed with HTTP Status 503: Service Unavailable"
Each Vault Client application will consume 1 connection. (Example 1 machine with 1x Vault Thick Client and 1x Inventor, runing and logged into Vault, will consume 2 connections)
Logged in but inactive clients release connections, which is then re-acquired following any client-server communication, such as browsing.
When mulitple users are connected to a Vault, the above error message will persist until the total number of connections to the Vault server drops below the defined limit, or the user logs into another Vault Server.
You can use the Windows Performanc Monitor to see the number of users who are connected to the Vault Server using the Web Service\ Current Connections Counter.
The instance selection will depend on if there are other websites running on the same server. For default Vault Server installations, selecting either the "_Total" or "Default Web Site" should be sufficient.
Autodesk regularly publishes White Papers regarding frequently asked-for topics such as how something works, best practices and optimising performance. There is a wealth of topics covered on the Autodesk Vault White Paper website.
"Geographically dispersed teams using 3D for clear design communication may struggle to collaborate effectively because sharing data using common Microsoft Windows file directories can take too long. Autodesk® Vault helps solve this problem by improving access to the latest designs even across global, wide area networks (WANs). When WANs exhibit high latency, the combination of Autodesk Vault and Riverbed® WAN optimization technology utilizing Steelhead®, a powerful data store and deduplication appliance, provides an effective solution to help maintain fast and efficient design data access. Tests performed by Autodesk illustrate the value of this combination—the addition of WAN optimization may dramatically reduce file transfer by up to 99% without further requirements to upgrade or replace existing software or hardware"