This PowerPoint will give attendees the tools for configuring and tuning the SQL Server and the Sage 500 Database to improve operational performance.

1. Configuring Sage 500
for Performance
RKL Performance Team

2. Hello, Does anyone have any advice for
speeding up the posting process in MAS? I was
posting a cash receipt and I timed it and it
took 1 minute and 36 seconds from start to
finish after all the reports printed and I
clicked "post." It has never taken this long in
the past.... any ideas as to why its so slow
the past couple of weeks?

3. Mid-Market Performance Tuning:
Zero human wait time…
for humans doing the right things
John Puttman - 2020

4.  IT Professionals Supporting Sage 500 Systems
 Sage 500 Functional Understanding
 SQL Server Administration
 Server Administration
 Business Professionals
 Will provide references for use by IT Professionals
Target Audience

5.  Sage 500 Specific Configuration – 16 Items
 VM and Server Configuration – 8 Items
 SQL Server Configuration – 5 Items
 Database Configuration – 5 Items
Agenda

6. Sage 500
SPECIFIC CONFIGURATIONS

7. #1 - TRUNCATE WORK TABLES
https://www.rklesolutions.com/blog/how-to-truncate-wrk-tables-in-sage-500-erp
• Primarily Defined by suffix of “wrk”
• Not always properly cleaned
• Create Nightly SQL Agent Job – Truncate Work Tables

8. #2 – MAINTAIN tglPosting
• Used in Pre-Posting process to create pending GL records
• When Posted will be removed from tglPosting and moved to tglTransaction
• Have found years of orphaned records
• Remove records that are more than one year old
• Remove records from periods that are closed
• To reduce risk – place records into archive table

9. #3 – MAINTAIN LOGGING TABLES
• tciDBActivityLog
• tciMaintAuditLog

10. #4 – Remove Orphaned Picklist Records
• tsoPickList
• Weekly SQL Agent Job

11. #5 – TURN OFF AUTO LOAD OF BUSINESS INSIGHTS VIEWS AND
LOOKUPS
https://www.rklesolutions.com/blog/sage-500-disable-auto-load

12. #6 – CONVERT STOCK STATUS BIE to STORED PROCEDURE
https://www.rklesolutions.com/blog/sage-500-disable-auto-load
• Use Dynamic SQL to handle Filtering
• Ensure that the final select includes CompanyID and all the
columns required for the view

13. #7 – REFACTOR spimIMSQtyAvail
https://www.rklesolutions.com/blog/sage-500-process-replenishment-orders
• Especially important when using Inventory Replenishment
• Native Logic for Quantity on Hand, Pending Increase and Pending Decrease has 3
overflow checks and the query
• Refactor to 1 query with try catch and 2nd query for overflow checks
• Decreased Create Suggested Orders runtime 5 – 10 times
SHOW DEMO SCRIPT – Refactor spimIMSQtyAvail.sql

14. #8 – REFACTOR spimCalOwnDemand
• Approximately 10x change for
Calculate Projected Demand
• Native Code – Nested Loops
• RKL Set Based Refactor
• Refactored code can easily be
tested against native
SHOW DEMO SCRIPT – Test spimCalOwnDemand_RKL.sql
Related Scripts:
spimCalOwnDemand_RKL.sql and Test spimCalOwnDemand_RKL.sql

15. #9 – REFACTOR LOGIC LOCK CLEANUP
• Assists in Shipment Commit Process
• Courtesy of Filipe Miranda – a DBA at one of RKL’s customers
• Refactor spsmLogicalLockCleanup
• Add SQL Agent Job to asynchronously cleanup locks
• Did not see this procedure called by any other processes or with a different lock
type.
SHOW DEMO SCRIPT:
spsmLogicalLockCleanup – New Version.sql

16. #10 – Automate Customer and Vendor Aging
• Courtesy of Russ Griffith – RKL’s Sage 500 Practice Manager
https://www.rklesolutions.com/blog/sage500-automate-aging-recalc

17. #11 – Automate Shipment Commit Process
• Courtesy of Dan Perrigan – RKL Sr Sage 500 Developer
• Implemented at several Sage 500 customers
• Can be scheduled to run throughout the day or in the evenings
• Can include or exclude invoice posting
• Saves operator time in committing shipments and or posting invoices
Contact RKL eSolutions Consulting for quote

18. #12 – Consider Running on a Newer Version of SQL Server
• Sage 500 7.2 running on SQL 2014
• Sage 500 7.4 running on SQL 2017
• SQL 2016 Benefits
• Query Store
• SQL 2019 Benefits
• Adaptive Query Processing
• Script to correct version checking – Turn off SQL Version Ckg-force version.sql
(Note – 7.6 with O2 Mobile has code issue with SQL 2012+)
https://www.rklesolutions.com/blog/running-sage-500-7-2-on-sql-server-2014

19. #13 – eBusiness Suite – Sales Order Search
• Older versions of eBS – The main sales order search query has a few non sargable
predicates causing table scans on several tables and resulting in > 20 second return
times.
• Modifying to use a dynamic sql improves performance to < 1 second return times
SHOW DEMO SCRIPT:
eBS – SPSOSEARCHORDER_dynamic_RKL.sql

20. #14 – eBusiness Suite – Customer Search
• Older versions of eBS – One query has a few non sargable predicates causing table
scans on several tables and resulting in > 10 second return times.
• Modifying to use a dynamic sql improves performance to < 1 second return times
SHOW DEMO SCRIPT:
eBS – SPARGETCUST_RKL.sql

21. #15 – eBusiness Suite – Sales Order Insert
• Older versions of eBS – sales order insert has a check for existing address. It has
non sargable predicates. Insert times can be > 10 seconds
• Modifying to use a CTE and improve times to < 2 seconds
SHOW DEMO SCRIPT:
eBS – SPSOINSERTSTGORDERBASIC_RKL.sql

22. #16 – O2 Mobile Implementations: Maintain toaEvent
• In some versions of O2 mobile toaEvent doesn’t empty
• Some customers have > 3 million rows in the table
• Adding new rows to the table can take 4 seconds to complete do to a lookup
• Add SQL Agent Job to remove old records to speed performance

23. VM & Server
CONFIGURATION

24. #17 – BIOS CONFIGURATION
• Power Management Settings – Disabled
• Disable C-States
• HyperThreading - Enabled

25. #18 – VMWare Guest OS Configuration
• Compute
• CPU configuration to match physical Host
• If possible stay within one NUMA node
• Hot CPU – OFF
• Make sure to configure change default of one socket per vCPU
• Memory
• Stay within one NUMA Node
• Reserve all guest memory
• Network
• Turn off the “Allow the computer to save power setting”
• Turn on Receive Side Scaling

26. #19 – VMWare Guest Storage Configuration
• SCSI Adapters – use the VMWare Paravirtual Adpaters (PVSCSI)
• Spread Drives across multiple adapters
Drive Controller /
Location
Purpose
C: 0:0 Operating System
D: 1:0 SQL Data Files
L: 2:0 SQL Log Files
T: 3:0 TempDB Data and Log Files
Z: 0:1 Backup

27. #20 – SSD Prioritization
• T:TEMPDB
• L:LOG
• D:Data
• C:OS
• Z:Backups

28. #21 – Service Accounts
• Use Group Managed Service Account or Managed
Service Account
• Domain Account as alternative
• Use separate accounts for Dev, Staging and
Production
Microsoft Guide to gMSA: https://bit.ly/3e6drsO

29. #22 – Windows Power Options
• Use High Performance

30. #23 – Group Polices
• Add SQL Server Service Account to:
• Lock Pages In Memory
• Perform Volume Maintenance Tasks

31. #24 – Anti Virus Exclusions
• Configure any AV software to exclude SQL Server Files
• Binaries
• Data Files (.mdf, .ndf)
• Log Files (.ldf)
• Backup Files (.bak, .trn)
• Extended Events or Trace Files (.xel, .trc)
Microsoft SQL Server Guidance on Anti-Virus: https://bit.ly/2ypXxdC

32. SQL Server
CONFIGURATIONS

33. #25 – Trace Flags
• For All SQL Server Versions:
• T3226 – Disables Successful Backup to SQL Logs
• T4199 – Allows use of Optimizer improvements after RTM
• 2008, 2008 R2, 2012, 2014
• T1117 – Grow files equally as a group
• T1118 – Full Extents Only
• T2371 – Dynamic Statistics Auto Update Threshold
• 2016+
• T7745 – Query Store Shutdown with No Wait
• T7752 – Query Store Asynchronous Data Load

34. #26 – Memory Settings
• Assumes no other applications are running on the server
• Assumes no other instances of SQL Server are on server
• Max Memory – Leave 4 – 10 GB to OS depending on number
of connections
• Min Memory – ½ Max Memory

35. #27 – Parallelism Settings
• Cost Threshold for Parallelism: 30 – 50
• MAXDOP: Equal to number of CPUs on one NUMA Node

36. #28 – Other Server Settings
• Compress Backup by default: checked
• Optimize for Ad Hoc Workloads: True

37. #29 – TempDB
• Start with number of data files = number of processors / or 8 whichever is less
• Expand as needed by groups of 4 data files
• 80/10 Principle for avoiding intermittent growth
• 80% of tempdb disk space to data files
• 10% of tempdb disk space to tempDB log file

38. Sage 500 Database
CONFIGURATIONS

39. #30 – Statistics Generation
• Auto Create Statistics = True
• Auto Update Statistics = True
• Auto Update Statistics Asynchronously = True

40. #31 – Query Store
• SQL Server 2016+
• Operation Mode: Read Write
• Max Size – 2048 MB
• All other settings default

41. #32 – Missing Indexes

42. #33 – Index Fragmentation

43. #33 – Table Compression
• Only if you have CPU headroom
• Saves IO
• Save Memory
• Analyze for Row or Page compression
• Look at Largest Tables first

44. Questions?