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.

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.