Morning Maya,

> Running a report, which just executes one large query, that returns many rows, seems to be fine. It's the opening of a screen that executes 5-10 queries to get various information from various places that seems to be the main problem. (changing the program to a single query isn't really viable)

That one screen doesn't do something "silly" such as login, execute
query, logout, login execute another query, logout and so on? I once had
an application which did exactly that on *every* screen. Killed the TCP
ports as there were multiple users and the timeout period from when a
port closed until it was available for use again meant that there were
no ports available at busy times. :-(

> They are using Windows 2008 server.

How long has the server been running? I know that there are discussions
around that state that any Windows server should be rebooted "regularly"
for various reasons. How valid this is, I don't know as I'm not a
Windows guru.

> Any ideas as to what else I can look at?

It may sound silly, but has the server been configured to *not* run the
screen saver, or at least, not run one that demands CPU time?

Equally, is there anything running that shouldn't be - performance
monitor etc etc?


I can't think of anything else at the moment.


Cheers,
Norm.

--
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL

Company Number: 05132767