Opera 3 SQL SE Performance Issue

tcyprys

Just wondered if anyone else has had performance issues with Opera 3 SQL SE?

I have a site that is fairly locked down, and we moved them across to SQL SE around March. They are experiencing performance issues and slowness, resulting in the 'Switch to/Retry' message constantly occurring. Pegasus are looking at it but just wanted to see if anyone else had sites experiencing this.

The setup is that the Opera server is separate from the SQL server, both are VM's on the same physical machine. 

The 'Switch to/Retry' appears to get worse the longer you process, so that when I testing a process, the first hour hardly any occurrence, the second and third hour got progressively worse. Even a simple SOP Invoice reprint resulted in a wait for the publisher screen of around 2-3 minutes.

Initially, just asking the question if anyone has seen this... although any advice welcome!

Cheers

Tony

alex

Hi Tony,

We have a site with this exact issue when the payroll update is running. They are a heavy payroll user and the update takes between 2.5 and 3 hours to complete. They can't run it out of hours unfortunately. We've found that finance users (sales/purchase/SOP/cashbook) are affected whilst the update is running and get Switch To/Retry popups or just 'Not Responding'.

Their setup is:-

- Application server - this is where Opera 3 SQL SE v2.93.01 is installed. This server is running Windows Server 2019 Standard with 32gb RAM.

- SQL Server - this is where MS SQL Server is installed. This server is also Windows Server 2019 Standard with 32gb RAM. MS SQL Server 2019 is installed.

- RDS Servers. Users run Opera from two different RDS servers. Both servers are Windows Server 2019 Standard with 32gb RAM. Users on both RDS servers receive the Switch To/Retry popups.

I'd love to hear any ideas or solutions you've come up with!

Thanks,

Alex