About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A desktop application that worked well in the office can become slow when only its database moves to a hosted server, because some applications make a long series of small requests to the database for each screen. Inside an office network each request returns almost at once; across the internet each one waits for the round trip. Before moving, count the round trips behind one common screen that the program waits for one after another, multiply by the measured round-trip time, and if the answer is too slow, move the program next to its database, for example onto a hosted remote desktop, rather than splitting them.
Why it matters
Splitting looks like the simplest migration: move the server, keep the PCs as they are. When the application is chatty, the result is a system that works but feels broken. Screens that opened instantly take seconds, end-of-day reports stretch, and staff conclude the new hosting is slow when the server itself is idle. Some file-based databases add a further risk: data damage.
How it works
Small requests, multiplied
Microsoft's architecture guidance names the problem the Chatty I/O antipattern: "The cumulative effect of a large number of I/O requests can have a significant impact on performance and responsiveness." One of the causes it lists is "Reading and writing individual records to a database as distinct requests".
The arithmetic is simple. Illustrative example: a customer screen that makes 300 small database requests one after another spends about 0.3 seconds waiting at 1 millisecond per round trip in an office. At 20 milliseconds to a hosted server, it waits about 6 seconds. Nothing about the server has changed; only the distance.
The software-side fix is not yours to make
Microsoft's fix for chatty code is: "Reduce the number of I/O requests by packaging the data into larger, fewer requests." That is a change to the application's code. A business running a packaged accounting, practice-management or industry application cannot rewrite it, so the practical lever is placement: where the program runs in relation to its database.
File-based databases are a special case
Some applications keep data in a shared file rather than a database server. Microsoft Access is one example with published guidance. Microsoft's deployment guidance warns: "Avoid using an Access split database in a WAN or with Azure file shares because performance can be slow and databases may become corrupt." The supported alternatives it lists include linking to data held in "SQL Server or Azure SQL", and Remote Desktop Services.
Within an office, splitting still helps: Microsoft notes that in a split Access database performance "usually improves significantly because only the data is sent across the network". The warning is about stretching that split across a wide-area link.
What to choose and why
Count before you move
- Pick one screen staff use constantly, such as opening a customer or entering an invoice.
- Ask the vendor how many database requests it makes and whether the application supports running over a wide-area link. Some vendors publish this; others will answer if asked.
- If the vendor cannot say, have your IT provider measure it in a test copy using the database's own activity monitoring. Label this a research step and do not run it against live data without approval.
- Multiply the sequential round trips by the round-trip time measured from each office. Requests the application batches or sends together do not each add a full round trip, so this is an estimate to confirm by testing, not an exact formula.
- Decide whether the result is acceptable for that screen.
Placement options
| Option | When it fits |
|---|---|
| Program and database both hosted; staff use a remote desktop | Chatty or file-based applications; mixed office and home staff |
| Program on office PCs, database hosted | Application vendor supports wide-area use and counted round trips are acceptable |
| Web version of the application | Vendor offers one with the features you use |
| Program and database both stay in the office | Short term, while one of the above is prepared |
The table is editorial guidance; the vendor's supported configurations decide.
Illustrative example
A 25-person distribution business moves its server to a hosting provider but keeps its stock program installed on each PC. Opening an order now takes eight seconds instead of under one. The vendor confirms the program makes several hundred requests per order and supports wide-area use only through a remote desktop. The business moves the program onto a hosted remote desktop beside the database, and order screens return to about their old speed. The example is illustrative.
Read next
Related articles you may want next.
- HostingWhere should hosted servers be? Measuring latency from your offices firstMeasure network delay from each office before choosing a hosting location. Understand remote desktop guidance, application sensitivity and how to collect useful timings.Read article
- HostingSQL Server and the application on one server or twoWhen running a business application and its SQL Server database on the same hosted server saves money, and when it causes memory contention, extra per-core licensing, wider security exposure and coupled outages.Read article
- HostingHosted file storage: a file server VM, SharePoint/OneDrive or the office NASHow a business decides where shared files live after moving its applications to a hosting provider: a file server alongside the hosted servers, SharePoint and OneDrive, or the existing office NAS, using Microsoft's documented sync limits and an inventory of how files are used.Read article
Risks and limits
- Remote desktops bring their own costs. Licences, session host sizing and printing need planning; see related topics.
- Request counts vary by screen. One fast screen does not prove a slow report will be fine; test the heaviest routine too.
- Vendor support comes first. Running an application in an unsupported layout can leave you without help when it fails.
- File-based databases risk damage, not only slowness. Microsoft's warning about Access mentions corruption; treat any file-shared database across a wide-area link with the same caution until its vendor says otherwise.
Sources
Opened 15 November 2026.
- Microsoft Learn, Azure Architecture Center: Chatty I/O antipattern, updated 23 October 2026.
- Microsoft Support: Deploy an Access application, updated 15 September 2026.
- Microsoft Support: Split an Access database, updated 15 September 2026.
Related service: Cloud hosting.
Learning notes
- A chatty application waits a round trip for each request it makes one after another; distance multiplies that wait, while batched requests share one.
- Microsoft's fix for chatty code is fewer, larger requests, which only the software vendor can make.
- For packaged software, the lever is placement: keep the program next to its database.
- Microsoft warns against stretching a split Access database across a WAN: slow and possible corruption.
- Count the sequential round trips behind one common screen and multiply by measured round-trip time as an estimate before moving; confirm by testing.
This article was originally published on .