Currently have a SBS 2011 setup with 5 local users that use Sage Line 50 2013 (data folder held on SBS 2011).
I also have a TS/RDS Server 2013 setup for 4 remote users for Booking s/ware and 2 remote users for Sage Line 50 2013.
We having occasional issues with slow speeds and ‘file waiting’ using Sage Line 50 2013 – a common problem with Sage across a network. Sage support have suggested upgrading to Sage 200 (at a cost of approx. £16k!), for a lot of modules we won’t use. Doing a bit of research pointed me in the direction of perhaps using RDS locally for Sage Line 50 2013 and store the Sage data files locally on the RDS aswell – thus eliminating the networking issue, as all local and remote users would remote in (most probably using RemoteApp).
So my question is on the build side. I’ve tested Sage Line 50 2013 on a number of machines using their local stores and my i7-2600k/8GB/SSD machine out stripes them all by a long way. So I was going to build a new server based on similar spec with:
SSD x2 (Raid 1) 240GB or 480GB
Windows Server 2012 + Appropriate Std. Cals/RDS Cals
[Approx. cost £2k/£2.5k.]
I know most will say don’t build, but you get so much more for your money and this is a local server where I am based so support isn’t an issue. Also I know a few will question SSD setup, but I’ve been using SSD’s in Raid1 in the SBS 2011 server for 2 years now and it’s been rock solid. Also its possible overkill, but if it’s able to speed up running reports by 30 seconds a time, it’s well worth the cost against labour waits particularly costing out Managing Directors and Financial directors wages.
So couple of questions:
Firstly is there any issues with running Sage Line 50 2013 over RDS to this level.
Is the above build appropriate for a potential 11 (current) – 15 (potential) users remote’ing in.
As always, thanks for any replies.