We store Sage 50 data and Sage Payroll databases on a network drive. e.g. T:\Sage Payroll.
The programs run from the local C: Drive.
The performance is dreadful and only improves if we move the data to the C: or another local drive.
We have gone trhough all of the Sage suggestions with no success and our internal infrastructure is very good.
Security products are not the issue as we have tried disabling all of these.
Moving to the Cloud is not a solution to this problem. I have to work with what I have.
Does anyone have these products running in this way with a reasonable level of performance? Or is Sage on a network just a big bag of bolts?
Thank you,
Paul
Related resources
Replies (10)
Please login or register to join the discussion.
From memory i think they always said dont save on network drive.
Have you tried saving on one computer and accessing that file from other computers?
Is sage cloud50 not an option - its not really saving on then cloud as such its saved similar to sage50 with options to formally access from elsewhere.
From memory i think they always said dont save on network drive.
Have you tried saving on one computer and accessing that file from other computers?
Is sage cloud50 not an option - its not really saving on then cloud as such its saved similar to sage50 with options to formally access from elsewhere.
Sage payroll on a network is (painfully) slow - but, as you say, you have to work with what you have.
I am currently in the same situation - but am exploring an exit path on the payroll side.
Haven't used Sage 50 for a fair while, but no reason to assume it is any better than payroll.
Is the data stored on a server or another PC you are trying to the data file from?
If I recall when running off a server they had an addon product can't remember what it's called and it basically had to show a connection to the server.
Also when browsing to the data rather than selecting the drive from my computer then T:, try browsing to the data from under 'Networks'.
Your problem is probably shared by all others who have it on a shared network. If you don’t need it on a shared network then don’t have it there. IT’s demand to have it on one isn’t a reason either. Avoid it if you can keeping security in mind of course.
I think the local drive will just be your software application - not the ledgers.
Pretty much all of my Sage 50 accounts clients run the software over a network with no problems. It is odd that you say that both accounts and payroll are slow as their databases and means of accessing the databases are completely different and share nothing in common so, if they are both slow, it would suggest that the problem is more likely to be network related than software related.
I know you mentioned that you've tried disabling security software but one thing that can definitely cause speed issues is if the folder that the data is stored in is being scanned by your AntiVirus software, those folders should always be excluded.
John
As you say, the data files are fundamentally different yet both are slow, so that can't be it.
AV exclusions are in place, although as a concept, I am not happy with the idea.
We even built a minimal server just to test it.
I was wondering if it might be something to do with how file sharing works.
The data files are different as is the data access method, so if the issue is caused by something Sage side rather than by your IT infrastructure then there are likely to be two different causes.
It would be useful to have a bit more information, say:
* the size of the accdata folder for Sage 50 accounts and the mdb file for Sage 50 payroll
* some indication of what specific actions are slow, and how long some of the actions take
* what's the minimum link speed
* does the server have hard disks or SSDs
Alternatively if you'd like to direct message me, I'm happy to spend 10 or 15 minutes talking things through.
Jonathan
FWIW I have a client running Line 50 off a server (local application - just the data on the server). Speeds are fine. So it can be OK.
Some years ago they went through a phase of being slow. I cannot remember now how it was solved; it may have been as simple as a change of server.