The following recommendations should deliver adequate performance in each indicated category. If your implementation is particularly demanding, you want better than just "adequate" performance, or your database is large, you should increase both RAM and processor speed to compensate. Simultaneous usage of resource-hungry applications such as Microsoft Office also demand more RAM.

Network Server

• A server running Windows 2003 Server, Windows 2000 (Service Pack 4 or later), Windows XP, or Windows Vista. Installation of the database on a Novell server or on older versions of Windows is no longer supported. In all cases it is recommended that the designated server computer not be used simultaneously as a workstation and as a server. Performance, database security and integrity are compromised when the server doubles as a Workstation.
  
• Windows 2000 servers should have no less than 512 MB of RAM; XP servers and Server 2003 systems should have no less than 1 GB of RAM.
In general, additional memory is more important than a faster processor, but processor speed is important, particularly in larger networks. The amount of RAM recommended is directly proportional to the size of your data set. Large transaction volume organizations should think in terms of at least 1 GB, and the database will use multiple processors to improve performance, if present. The basic server license permits installation on servers with up to four processor cores. For larger servers, contact SOS for licensing details.

• Hard drive space proportional to the size of the organization. Assuming that an average patient account includes about 20 journal entries (charges and credits), you should estimate at least 35K - 70K per patient, or 35 MB - 70 MB per 1,000 patient accounts, plus up to 400 megabytes for the program files. SOS would recommend that you double this figure to allow ample space for temporary tables, transaction logs, and other needs. Use of both SOS OM (receivables and billing) and CM (clinical records) will increase the amount of drive space required.
  
  
Performance and data safety can be enhanced on an active system through the use of multiple hard drives, with the transaction log stored on a second drive in the same server and perhaps the index files on a third drive. Moving the transaction log to a different drive is straightforward (instructions can be found in the technical reference, SOSTECH.PDF, located in the SOS folder) but relocating the index files requires unloading and reloading the database with a custom reload script. If you would like to implement a more complex installation of this sort, call SOS to discuss whether such a modification would be worthwhile. By default, all program and data files will be installed on the same drive.

• 600 MHz processor or higher. The database will take advantage of multiple processors, if present. Larger databases will require faster processors.
  
• SOS’s standard network license permits use of up to four processor cores in a database server. If you have a larger server and want to use more than four processors to run the database, contact SOS to extend your license at very reasonable cost.
  
• 512 MB or more RAM (highly dependent on size of database, but 512 MB is the minimum that should be considered). Additional RAM is always a good investment.
  
• One or more high performance hard disks. Ideally, the database files should be located on a separate, dedicated partition on a drive other than the primary system drive. See document #435 in the SOS Document Library for specifics (http://www.sosoft.com/html/document_library.php).
  
  If setting up a dedicated database server that will not also be used for file or printer sharing, you may use a Windows 2000 Pro or Windows XP Pro system to host the database. That is also a possiblity if setting up a small "peer" network with 10 or fewer users. It is neither required nor recommended to configure a network share for the database. All communication between the workstations and the database is done through IP messaging, without any need for users to log into the database server computer. As a result, the Windows 2000/XP Pro limit of ten concurrent users does not apply for SOS database access.
  
• CD-ROM, CD-RW, DVD or DVD-RW drive.
  
• Tape backup or a similar robust backup system that permits easy media rotation and off-site storage of archival backups. Depending on the amount of data to be backed up, some installations will be able to use writable CD or DVD, or removable cartridge such as Iomega Zip or Rev instead of tape.