1. Get better hardware

2. Rebuild the database indexes

1) pretty beefy server I figured: 
Dual 2.3GHz
256GB RAM
All drives are SSDs
Separate VM for MSSQL with two dedicated SQL data drives in raid 10.

2) How might we rebuild the database indexes. Somewhere in sage or in MSSQL? 

This is what we keep.  We use a combination of built in purge functions and also custom scripts.  You can't just keep throwing more and more hardware at something like this.  We process hundreds of transactions a day so the data can quickly get out of hand as there is so much duplicate information.

Indexes in SQL.  Since you have SSDs, the slowness is probably your network.

Its all on the same machine in different VMs. 

Including where we are accessing the UI form.  That is a terminal services VM.

Will review the Indexes.

This is a helpful rubric to keep as we explore pruning.

VMs often suck

https://ola.hallengren.com/

I recommend this tool/script.  Works good for SQL Express clients, too.

The built-in functions for rebuilding indexes are all easily scheduled.

When attempting O/E/ clear history, for Transaction history, any year other than 2022 give error: "The date entered lies outside the range specified in the company profile.

This is a normal message. Simply click OK to continue. The data is verified by the "Warning Date Range" found in Common Services - Company Profile - Options. 

We have a Purge History utility that will simplify the clear history process. 

www.musick-int.com/.../index.HTM

Hi Mike,

can u help with the purge functions and scripts to do this? 

thanks

We have a Purge History Utility that makes clearing history in all modules very simple. 

www.musick-int.com/.../INDEX.HTM

I always create an archive company that is "Pre history clearing "  that is still accessible on the sage start list.  Murphys law is that as soon as you clear anything someone will ask for it.

so true. great thought