SQL Server specs?

Network specs?

Database size?

Index rebuilds?

As Jay indicates, database size and hardware are very important

I recommend to my clients that they open OPS Inquiry -> Item Inquiry early in the day and leave it open until they sign out of Accpac - usually only the initial load of OPS takes a long time since it has to open all of the associated views - once opened the views are quick to pull data up

Hi all

This is getting worse so have answered the queries below

SQL Server specs? SQL server 2005

Network specs? no virtualisation, users access via terminal server - server 2008

Database size? 20 gig

Index rebuilds? nightly

15 users would have Ops inquiry open out of 30 logged into Sage, processing heavily orders and shipping all day.  Ops Inquiry just seems to be really really inefficient in its ability to pull up data, you should be able to restrict the history it looks at.  We are considering archiving off data but we should have to.

I also append my original post to that this user is Sage Accpac 5.6

Thanks

What is the amount of RAM on the server and what other software runs on it?  Is this Server just an MS SQL server?  I'm assuming it's not running MSDE, correct?

What functions in Ops Inquiry are they using - Item Inquiry, Order Inquiry, Custom searches, etc.?

One of my clients decided to archive some data and that assisted with performance of the Item Inquiry.

I had the same issue at a site, I change to server from data source in database setup and the speed improved.

Hi Stacey,

Thought I would bump this thread. We have a client with a fair sized database, same grinding speed issues in Ops Enquiry. After much back and forth we had this reply from Sage:

"I heard from the NA Consultant.

I confirmed with our specialists.  Unfortunately, there’s not much that can be done for this when the data is large.  There is no setting in Sage 300 ERP or in SQL that will speed this up.

The only workaround is to let the window load once and don’t close it until it’s time to log out of Sage 300."

So its NOT about the version of Sage, SQL, etc etc. Although massive beasty servers wouldn't hurt, obviously.

My take is that its about the data that Ops Enquiry has to wade through that is either poorly indexed or not indexed at all.

Ive created an ideas thread to ask for indexing - please vote if you can.
https://www5.v1ideas.com/TheSageGroupplc/Sage300ERP/Idea/Detail/25577

Thanks Will , have Voted

Hope you all well