Many businesses assume that if staff can access email and files over a VPN, they can also run Sage 200 the same way. Unfortunately, Sage 200 is very different.
Unlike cloud applications, Sage 200 is a client-server application that constantly exchanges data with its SQL Server database. This communication is designed for a fast local network where latency is typically less than 1 millisecond.
A VPN introduces much higher latency—often 20ms to 100ms or more. While that might not sound significant, Sage 200 performs hundreds or even thousands of database requests during normal processing. Each request has to travel across the VPN and wait for a response, causing delays that quickly add up.
It’s Not Just the Remote User Who Is Affected
One of the biggest misconceptions is that a slow VPN only impacts the person working remotely.
In reality, Sage 200 relies on SQL Server transactions to maintain data integrity. During many operations, SQL temporarily locks records, tables or indexes while updates are completed.
On a local network, these locks usually exist for only a few milliseconds.
Over a VPN, the same operation may take several seconds because every database request is slowed by network latency.
While those locks remain in place, other users may be forced to wait.
This commonly affects tasks such as:
- Posting invoices
- Updating stock records
- Allocating receipts
- Processing sales orders
- Running period-end procedures
Unstable VPN Connections Make Things Worse
If the VPN connection is slow or unstable, problems can escalate quickly.
You may see:
- Sage appearing to freeze
- Long delays when posting transactions
- SQL blocking chains
- Deadlocks
- Locking or timeout errors
- Reduced performance for every Sage user
The issue is often mistaken for a slow server when the real cause is network latency.
Think of It Like a Single-Lane Road
Imagine a single-lane road controlled by traffic lights.
Office users drive through the junction almost instantly.
A VPN user moves much more slowly. While they’re in the junction, everyone else has to wait.
As more remote users connect over VPN, congestion increases and everyone’s performance suffers.
The Recommended Solution
Both Sage and Microsoft recommend that the Sage 200 client should not be run directly across a VPN.
Instead, remote users should connect to a desktop environment located on the same network as the Sage application and SQL Server, such as:
- Remote Desktop Services (RDS)
- Windows Terminal Server
- Azure Virtual Desktop
- A hosted desktop solution
With this approach, only the screen image, keyboard input and mouse movements travel across the internet. All communication between Sage 200 and SQL Server remains on the local network, delivering much better performance and avoiding the locking issues associated with VPN connections.
Need Help with Remote Access to Sage 200?
If your users are currently accessing Sage 200 over a VPN, there are better, supported ways to provide secure remote access without compromising performance.
At Eventura, we design and support remote desktop and hosted Sage 200 environments that give users a fast, reliable experience wherever they’re working.
