There are many possible alternatives for an advanced configuration setup. Depending upon your document retrieval needs, workflow configuration, and your application setup, you may want to take a gradual approach to expansion and simply add to the basic configuration.
One of the simplest ways to improve performance is to separate the disk IO on your SQL server to establish more independent paths to disk. Microsoft recommends splitting your application database, transaction logs, and temporary databases across different
Disk-drives to improve and sustain database performance.
Note: Please refer to the following article for
information:
http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1262122,00.html
Additional considerations may include providing additional memory for the IIS and SQL servers along with a higher-bandwidth connection between these servers.
Bandwidth bottlenecks can make a system seem sluggish even if the hardware underneath the servers is more than adequate.
The DocuPhase Client Services Team can help determine your needs by comparing your environment with some of our existing customers. If you already have implemented DocuPhase and are starting to experience performance problems, we can also help determine the source of your problems and suggest hardware alternatives for remediation.
Note: The Application/Web Server contains both the DocuPhase
Application and the associated Web Services.
These web services can
be distributed across a number of server environments. However, a configuration
similar to the previous diagram (shown above) should be able to support a basic
DocuPhase system that expands up to 100 users.
Additionally, the database server should be dedicated to the DocuPhase database. The repository should be placed on a dedicated file server, but alternatively it can be placed on the Application Server or the Database server.
When reaching the threshold of the 100 user mark, it may be wise to move to a SAN device or another highly accessible and redundant external storage medium.