Thursday, February 6, 2014

Optimizing SAP Business One Performance

I get a new job as an Administrator SAP Business One. The first time I did was to optimize the performance of the server and make loading time faster. From the test results that I did, the time it takes to open the SAP database directly from the server only 7 seconds. Meanwhile, when I open it from the client computer takes approximately 3 minutes. I'm sure there are things that cause the connection from the client to the server is not running well. After looking at various sites on how to accelerate the SAP Business One client connections. I found the following tips:

  • Refer to the Optimizing the SQL SAP Database.pdf you can find on the SAP Business One partner page and forum. 
  • The communication between the Terminal Services server(s) or Citrix server(s) and the SQL server should be at minimum of 1gig. You can purchase an inexpensive Dell 3-4 port 1gig hub or equivalent for around $200.00 and install it on the Business One server(s) and see a huge increase in performance. 
  • Create a .BAT file and put it in the startup for the Citrix or Terminal Server servers to delete .TMP files in the %userprofile%\local settings\temp folder at startup. 
  • Make sure all SQL queries, as well as any other remote access to the database, use the (NOLOCK) command next to each table accessed, otherwise it accesses the tables with a share lock. You could easily be locking thousands of records and pages of the database without this. 
  • Microsoft Windows does not do a good job of freeing up memory, improper log-out’s, etc. Re-booting Microsoft servers at a minimum of once per week is important. 
  • Antivirus software on the SAP Business One related servers: Don’t check and download the latest updates and virus definition files during the day, do it at night only. Do not do system scans during the day, maybe do the full scans at night. The real time scans need to be scaled back so it doesn’t include the SAP Business One executable files as well as Microsoft SQL programs. Consider stopping the real time scanning for an afternoon and see how your performance is effected. Note: if a MS-SQL database get’s infected with a virus, which I’ve never seen yet, you have to restore the database anyway. 
  • Review your work station antivirus scanning and updates also. If they are running during the day, these scans or updates on the work station give the impression that SAP Business One is slow but in reality it is the work station causing the slowness. 
  • Identify all software that is running on the SAP Business One servers. Only install and run what is really needed. The SQL server shouldn’t have much running on it, besides SQL and MS-Fax. 
  • Review the event logs daily or as often as needed to verify proper setup and installation. 
  • Review the SAP Business One and SQL Service Backup schedules. Typically we recommend these backups occur at 6am, 7pm, and perhaps lunch. These backups will typically slow the system down so trade off’s have to be evaluated. 
  • Backups to tape will also affect performance while running. Typically we recommend that client’s perform backup’s to tape while users are not on the system or if you run 24×7 when the user count as at the lowest. Review all Microsoft Windows performance logs to make sure there are no issues that require correction. 
  • Setup and auto-run SQL database maintenance jobs each night. 
  • Run Raid 1 or Raid 10 on the disks that the databases are on. Raid 5 is one of the slowest configurations for just about any ERP or Business Management database, due to the added disk I/O for additions, updates and deletes. It just isn’t necessary and is not worth the negative hit on performance. 
  • In summary, you need to look at hardware, the network and other software that is running, just as much as you are looking at the database server and the business software. Unfortunately, when the business software is “slow”, the users think that is the problem, when in fact, a lot of the time it is other software and configurations that are the true problem.
Source : SAP-B1

Filled Under:


Post a Comment