allanp0220
Technical User
Hi,
Great Plains 5.5, 12 workstations running NT4, Windows 2000 server, 2.2G memory.
Periodically operators involved in invoicing particularly report that the system is running slow - and I've seen it, its really slow like one line of an invoice every 10 seconds.
Usually I stop and start SQL server agent and then reboot the server to clear out the server memory. At first we thought this cured it but it seems this is not always so. In fact the server can have 1.3G memory free and they can still report it running slow - other operators are aware of it but not affected to the same extent. Sometimes, just occasionally, they report that its running fine!
I should point out that our database is now reaching 8G. Does anyone think this is causing the problem, surely if this were the case then the server would be using its full memory before it slowed. Although we know it has to be reduced I don't want to call our consultants out at vast cost to reduce the data only to find we still have the problem.
I'm not really an IT Manager, just got dropped into the position but I know that your'e a really knowledgable lot can anyone point out some likely checks I can do to try and pinpoint the problem?
Many thanks
Allan
Great Plains 5.5, 12 workstations running NT4, Windows 2000 server, 2.2G memory.
Periodically operators involved in invoicing particularly report that the system is running slow - and I've seen it, its really slow like one line of an invoice every 10 seconds.
Usually I stop and start SQL server agent and then reboot the server to clear out the server memory. At first we thought this cured it but it seems this is not always so. In fact the server can have 1.3G memory free and they can still report it running slow - other operators are aware of it but not affected to the same extent. Sometimes, just occasionally, they report that its running fine!
I should point out that our database is now reaching 8G. Does anyone think this is causing the problem, surely if this were the case then the server would be using its full memory before it slowed. Although we know it has to be reduced I don't want to call our consultants out at vast cost to reduce the data only to find we still have the problem.
I'm not really an IT Manager, just got dropped into the position but I know that your'e a really knowledgable lot can anyone point out some likely checks I can do to try and pinpoint the problem?
Many thanks
Allan