Sage 50 2009 - slow

Hi,

A client of mine has Sage 50 2009 (ver 15). It runs via Terminal Services on Windows Server 2003 R2 (but the problem is at least as bad if it is run client > server on the LAN). The problem is when the Quotation list is selected and a Qoutation selected for printing, when you click on 'Generate Report' it takes a long time to show the preview  - a long time being 10 to 20 sec. I've ensured that the Anti-Virus is not scanning any Sage Files (recommended on other fourms). Sage seems to think that it's a network issue, but the problem is the same even if you sit at the Server and run it directly from there. Invoices and Sale Orders are a bit slow as well but not as bad.

Any help would be appreciated.

Thanks

We had the same problem and we attached a 'sisco 1gigabit switch' to the server for sage to run of, as recommended by sage. That seemed to do the trick. Talk to sage support they seem to have most of the answers.

It's a known slow database, even when everything network-wise is perfect and in your example it is still slow when run at the server console, so it's not the network.  One bit of advice is to try to minimise database size by archiving and removing dead accounts.

I believe that Accounts 2011 is on an SQL server database, and much quicker, particularly noticeable in multi-user operation.

Jim

Hi Jimmy, SAGE is well known for it's poor performance both in general operation and especially when running reports. The reasons for this are that SAGE uses a flat file database system and when running reports SAGE accesses multiple individual files to pool together the related information. We recently upgraded to SAGE Accounts Professional 2012 and we have seen an improvement in performance. We also saw an improvement with an increase to the system RAM.

I also supports Jim's comment on archiving previous years accounts.

Thank you for your responses.

I've looked up the latest Sage 50 versions and it seems that they are still not SQL.

Elliott, it's interesting that you found 2012 better.

My clients Server is 32-bit and has 4Gb ram (only 3.5GB usuable in 32-bit system). Do you think installing Server 2003 64-bit would improve performance?

Does anyone know if Pegasus Opera or TAS Books would be better?

Thanks again. Your comments are greatly appreciated.

Jimmy

I had a load of trouble with Sage at one time mainly because of the hardware in use. I think adding some 'Server Options' to the DHCP server helped. Do you have DHCP running on the server?

This was years ago but I think one of them was '046 WINS/NBT Node Type' being set to '0x8'.

Act! was another pain in the backside before they moved it to SQL Server.

Hi Jimmy,

We have SAGE installed on a Windows Server 2008 with 8GB although I do not think that just installing 2003 64Bit with more RAM will necessarily solve the issues. It might be related to the number of users of the Terminal Server box or indeed some other process that is consuming resources. I would be happy for one our engineers take a look at with you on a remote session and see if they can spot something.

Pegasus will need to be done through an approved dealer as I recall and I do not have experience of TAS Books.

Idea 1: Disable the Anti Virus Service for a controlled period

Idea 2: Is the disk space low?

Idea 3: Disk Defragmentation Levels?

And finally look at this resouce http://www.sbslimited.co.uk/sageslow.htm

-Elliott

Let me know how you get on.