10 tips for optimizing server and Commerce software performance
Block 1. Hardware and power supply
1. Using SSD instead of HDD
For the normal operation of the database (DB), high read and write speed is critically necessary, therefore the use of an SSD is mandatory. Using old HDD drives (especially with damaged sectors) leads to severe freezing and increases the risk of the database entering an emergency state (Suspect or Recovery Pending).
2. Control of free disk space
On the disk where the DB and program directories are installed, it is necessary to always maintain a sufficient margin of free space (preferably at least 15-20%). Disk overflow (especially of the system drive C) is guaranteed to lead to archiving errors, the inability to update the program, and critical failures in SQL Server operation.
3. Uninterruptible power supply (UPS)
A PC with a database (server) must be connected to a UPS. A sudden power outage is the most common cause of DB damage (transition to the Suspect state), damage to system database files (.ldf or .mdf), and data loss.
Block 2. Windows OS settings
4. Prohibition of sleep and hibernation modes
On the server or main PC, it is strictly forbidden to use sleep mode, hibernation, or configure automatic hard disk shutdown. The PC power plan must be set to "High performance" to avoid connection drops with the DB over the local network.
5. Antivirus and Firewall settings
Windows Defender and third-party antiviruses (Avast, 360 Total Security, etc.) often mistakenly block or quarantine the program's executable files (torgsoft.exe, TorgsoftLicenseService.exe, etc.). To avoid this:
6. Optimization of background processes and memory
Disable startup programs and unnecessary background services (Xbox Game DVR, OneDrive, Cortana). Do not use the server for web surfing: browsers (for example, Google Chrome) or messengers (Telegram) can consume over 2 GB of RAM, which will be critically lacking for SQL Server, resulting in a complete freeze of Torgsoft.
7. Regular server reboot
Set up automatic server reboot (via Task Scheduler) at least 2-3 times a week during non-working hours (for example, at night). This frees up RAM, resets hung sessions, and prevents system "slowdowns".
Block 3. Database and SQL Server maintenance
8. Moving the program to a non-system drive
It is advisable to place the program directory and database on the D: drive (or another non-system drive). If the program is already on the C drive, moving is possible according to a clear algorithm:
9. Using the full version of SQL Server
The free version of SQL Server (Express), which is installed by default, has hardware limitations: it uses only 1.4 GB of RAM and has a database size limit of 10 GB. If the database reaches 10 GB, the program stops or operates with critical delays. To solve this problem, you need to upgrade to paid versions of SQL Server (Standard or Enterprise), which do not have such limits.
Go back to the previous step