Below is the recommended hardware requirements for LinkSOFT Applications. Select the scenario that best suits your needs and seek advice from an authorized representative before making your purchase.
Select the overall class of server required for your environment. The table below is based on transaction volume and concurrent user requirements. In summary, here are the classes:
Entry-Level - minimum specification for running LinkSOFT - typically 1 or 2 stations per site
Mid-Range - mid-size customer needs - typically 10 POS stations per site with 1 or 2 sites
Enterprise 1 - high user counts, high volume situations - Typically 15 + stations per site with up to 10 sites in total
Enterprise 2 - higher user count, higher volumes - Typically 15+ stations per site with up to 50 sites in total
2. Transaction Volume
The transaction volume used for this calculation is the total monthly transaction volume estimate for all LinkSOFT applications. For this table,a transaction is a single line item on a business document. Thus, 100 invoices each with 5 line items is a total of 500 transactions, as is a single invoice with 500 line items.
3. Number of Users
The number of users parameter refers to the maximum number of users likely to be active at any one time. This number can be difficult to calculate since users can vary significantly in their demands on the system. A user running a report will use more server processing power and more disk activity than a user who enters an occasional purchase order. The figure that should be used for this table is an equivalent number of reasonably active users. If most users are highly intermittent, the equivalent number will be slightly lower; if most users will be running large, complex reports, the user count should increase slightly.
4. POS Stations Recommendations
Since POS stations will always be based on a single user, there are two categories, Entry level (< 15,000 transactions per month) and Mid Range (> 15,000 transactions per month). POS Stations can setup as a "Stand Alone" system, where the database resides on the POS station instead of a Backend Server
5. BackEnd Server Specifications
Each of the four server classes identified above is specified in more detail below. Within each class, a lower and higher specification is provided (except Entry-Level). The exact configuration can be chosen according to whether the user count and transaction volume is at the lower or higher end of table 1.
6. Database Backups
It is extremely important that your business information is backed up on a regular basis. The frequency and type of backup should be discussed with your implementation team, but one or more drives on the server can ensure a timely backup is completed. For large volumes, it is often possible to use more than one drive for the backup - reducing the time taken to complete the process. It is also possible to backup to the local disk, and then copy the file elsewhere for storage.
There are two backup processes that needs to be considered
Automated backups that the SQL Server agent runs and stores locally on a disk
Off site backup storage
For SQL Server agent backups, it is recommended that a separate drive is installed on the Database Server. This drive is a temporary drive to hold backups before they are taken off site for secure storage.
6.1 Database Performance
Relational Databases are advanced systems that sometimes require tuning for optimal performance. Since the introduction of SQL Server 7.0 and followed by SQL Server 2019, the database engine has become largely self-configuring and self-tuning. However, it is still useful to perform some level of tuning on a SQL Server database, particularly in the area of database input/output (I/O) operations to the physical disk subsystem. The driving focus of performance tuning is to reduce I/O so that buffer cache is best utilized. If performed by an experienced professional, tuning can substantially improve performance on your hardware. Note that there are many considerations, which are outside of the scope of this paper, that are involved in maintaining the server at peak performance.