This topic provides suggestions and possible causes for the SEOM to experience degraded performance. Some of the tips are software release-dependent or specific and may not apply to your environment.
- As the business grows, it may become necessary to move the SEOM data file to a dedicated server rather than using a host PC that is busy performing other tasks. If possible, use a server with a solid-state drive (SSD) to house SEOM‘s data file. Also, refer to System Requirements to ensure that the processor speed and RAM requirements of all servers and workstations are being met.
- Do NOT use ZoneAlarm Personal Firewall software.
- Check the settings of the anti-virus software installed on each workstation to see if it is possible to exclude MS Access from the list of programs and/or files it scans as they are opened and closed. Stone Edge Technologies Inc. suggests using the Microsoft Security Essentials software.
- Use a gigabit ethernet network (LAN or WAN). All network components must be capable of processing at that speed, or the user will not reap the benefits of increased performance. A network connection is only as fast as its slowest component. Ensure that the ethernet cables, routers, hubs, and NICs (network interface cards) that are being used support gigabit speeds. A High-speed ethernet cable is preferred.
- Compact an Access data file weekly after creating a backup copy.
- Run OM Compiler regularly on each workstation.
- Change the DefaultOrderView parameter (in the Program group) to All.
- Archive old data to reduce the size of an Access data file.
The Standard Edition of SEOM uses Microsoft Access as the back-end database to store your orders, customer, inventory, etc. The maximum database capacity for an Access .mdb file is 2GB (Gigabytes). However, based on how MS Access works in a server/client environment, the realistic, usable size for a SEOM data file is around 500MB-800MB. The reason for this is that whenever a client workstation requests the server housing the data file, the program must move the entire file to the client machine to service the request (i.e., copying an 800-megabyte file from one PC to another). This is a feature of MS Access and cannot be modified. Therefore, as your data file grows, it will take longer and longer to serve the client requests.
For clients who run stores that handle large volumes and do not wish to move to the “Enterprise” Edition of SEOM, many have made the change to Gigabit Ethernet (1000BaseT). They have found that this dramatically increases network performance and SEOM response times. For example, compare it to emptying a swimming pool through a cocktail straw (10baseT), then a drinking straw (100BaseT), and then a fire hose (1000BaseT). The more bandwidth that is available, the faster files can be moved.
Another solution is to use the SEOM‘s Archiving system to take a portion of the orders out of SEOM‘s current data file and put them into an “Archive” data file. By removing 6 – 12 months of old orders from the existing data file, you can drastically reduce the file’s size and restore lost performance. Many Stone Edge clients archive in 4, 6, and 12-month increments depending on the time it takes to fill the MS Access data file of 2GB.
- Add indexes to frequently searched fields (refer to Microsoft’s documentation for adding indexes to an Access or SQL Server database. Always make a backup copy of the database before adding or re-building indexes.
- If using a Shared or Local Stack, check the stack viewer (Ctrl+Shift+S key combination at the Main Menu) to ensure that records are not “stuck” there. Sometimes, a record can fail to be sent, and the program will exceed the limit of retries, but the program will never remove the failed record from the queue. All other records behind it in the stack remain in the stack queue, which continues to grow as new orders are processed, causing the program to slow down. Manually delete the “stuck” record from the stack queue.
A common reason for this happening is the user has the system parameter, UseGenericStatusUpdates set to TRUE in the main system parameters rather than in the cart-based parameters. When set in the main parameters, UseGenericStatusUpdates=TRUE causes the program to create status update records for every shopping cart in the current data file, whether or not the shopping cart requires that setting to send status updates. Any status records going to shopping carts that do not require UseGenericStatusUpdates=TRUE will fail, clogging the stack. Review the Updating Order Status documentation for each shopping cart to determine if it requires UseGenericStatusUpdates=TRUE and if so, set it in the Program group of the cart-based parameters. Leave the UseGenericStatusUpdates parameter in the main parameters set to FALSE, unless only one shopping cart is defined in the data file. It is one of the types that require it to be set TRUE.
Improving the Performance of Stone Edge
- Along the same vein, if the user has checked the Send Updates To the Order Status System box and they do not subscribe to that service, the stack will become clogged with records that cannot be delivered. This setting can be found on Page 1 of the Order Status System section of the Setup Wizard.
- Likewise, if only one shopping cart is defined in the current data file, and it does not support receiving status events at all, make sure there are no Status Events that have the Notify Cart box selected. Verify the status events settings by going to Main Menu > Settings > System Functions > Status Events.
- Stay current with Microsoft Service Packs and recommended hotfixes for Access and the operating system, as well. Make sure that they are being applied as well as downloaded to your PCs.
- As a last resort, try uninstalling the current version of SEOM and reinstalling it if the user has retained the installer for the currently installed version of SEOM. Stone Edge Technologies Inc. only provides the installer for the program’s latest version at the download gateway.
Note: Back up the SEOM data files, including email templates and custom reports, before uninstalling and reinstalling the program. Make sure all custom reports, forms, or queries are stored in the Custom Reports database. Use the key combination of Ctrl+Shift+C at the main menu to determine the location of files used by the program.