HAS THE PERFORMANCE PROBLEM BEEN ADDRESSED?

There are a significant number of posts about excruciatingly poor performance across a network of multi user Sage 2010.

I have a client on V10 who has been offered a good deal by sage to upgrade to version 17.  Does anyone know if the performance problems still exist?  Or have they been addressed now?

Any help greatly appreciated.

BRgds

Nigel

Comments

Performance...

johndon68 | | Permalink

There are certainly some areas that were known to be slow in v2010 that have been addressed.

The speed issue when accessing customer accounts in invoicing/ordering has been fixed (although there was an update for v2010 to fix this).  Statement production (using standard layouts) was also appallingly slow on v2010 and that has been fixed in v2011 although, again, there was a download available from the Sage website that fixed this issue as well.

John

Thanks

nkwayne | | Permalink

Thanks John, assistance appreciated.  Do you happen to know, is "version 17" Sage 2010, or is it Sage 2011?  Is version 17 pretty stable and reliable?

 

BRgds

 

Nigel

Witch-Queen's picture

Sage versions

Witch-Queen | | Permalink

2007 = V13

2008 = V14

2009 = V15

2010 = V16

2011 = V17

-- Witch-Queen

Stability

johndon68 | | Permalink

I've been using v2011 (17) in a 3 user network environment since it was released and, whilst we don't put a huge amount of data through, we've had no issues with regards to stability.

John

kevin503's picture

Sage 2011 performance- it depends...

kevin503 | | Permalink

I'd agree, v17 / 2011 seems to be stable enough now.

Performance? Data on local machine - no major problems.

Using as multi-user, with data on another machine, the outcome is less certain.

With large data sets, or making use of project facilities, price lists etc, you could see a big drop in performance compared to anything before v13. Not just reporting speed, but simple data entry can take far longer than you would reasonably expect.

The problem is Sage adding more and more bells and whistles on-top of a database architecture already long past its best. Every new feature and data-field comes at the expense of performance.

By all means upgrade your licence to 2011, it's a very good deal at the moment. But please get proper on-site assistance from a Sage reseller (ie. someone with Sage understanding AND IT skills) before actually considering installing the software.  Your server, PCs, network infrastructure and anti-virus setup should all be checked over before going ahead with this upgrade.

Sage 17

ghewitt | | Permalink

I have to agree; I am on v16 and it is sooo slow, so holding off from installing v17. Call up a customer record and wait for it to be populated. We are networked and so the impact is pretty severe; sometimes getting the pale-screen-of death. Not good when we really need it up and doing. Reports? Well. What can I say. As a by-the-by sage payroll is also crawling and all my reports that I had tweaked don't work. I am looking for alternatives, seriously. Maybe you should?

Performance tips V16 (2010)

ronnieh | | Permalink

A couple of tips for improving the speed of V16 across a network are:

  1. Make sure you have installed the updates available for V16 (3 available).
  2. Remove any reports you do not use, as if you are using reports from the server it has to populate the list every time you select the reports menu.

As for V17 I believe some of the speed issuses have been sorted but not all, we have not upgraded yet as the sagepay interface on 2011 is not as slick as 2010 due to new legislation regarding credit card processing, I'm told.

Ronnie

Sage network speed

Chessy | | Permalink
PostPosted: Sun Apr 10, 2011 4:00 pm    Subject: Sage Report problems with Windows 7 Reply with quote Edit/Delete this post
Sage have just issued knowledgebase article No, 27043 that admits there is a speed problem running Sage using a mixture of Windows 7 and XP machines.

As I read the article it is as follows. Windows changed the locking protocol from Vista onwards from protocol SMB 1 to SMB 2. Line 50 cannot cope very well with a mixture of these 2 protocols and Sage give the following 2 fixes:-

1. Force all your machines to use the older SMB 1.0 protocol. Sage say that you have to do this at your own risk as it could cause problems in other Windows programmes.

2. Upgrade all your PCs to Windows 7 / Vista so that they all use the new protocol. If you are running Small Business Server 2003 you would also need to upgrade it to SBS2008 as SBS2003 uses the old protocol.

Add comment
Log in or register to post comments
Group: Sage 50 Accounts discussion group
An independent forum for Sage users to share ideas, tips and gripes