Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Growing from 10 to 60 staff: the limits to check before they force a hosting redesign

Technical article
Hosting

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.

There is no staff number at which a hosting redesign is forced. What a growing business meets instead are limits that grow with it: a free database edition that caps database size and memory, remote desktop licences needed for every user or device that connects, and single points of failure that may be acceptable for ten people but cost far more for sixty. Map each limit against the three-year headcount and data plan, and schedule the change for a quiet period before you reach it.

Why it matters

A limit found during growth arrives as an outage or a compliance problem: a database that stops accepting data, new staff who cannot sign in, or one server failure that stops the whole office. Each of these is predictable from published figures. A one-page threshold map turns them into budget items.

How it works

Database edition limits

Some business applications install SQL Server Express, the free edition. Its limits are published:

  • SQL Server 2022 Express: compute "Limited to lesser of 1 socket or 4 cores", buffer pool memory of 1,410 MB, and a maximum relational database size of 10 GB.
  • SQL Server 2025 Express: the same compute and memory limits, but Microsoft's 2025 table lists the maximum relational database size as 50 GB.

These limits are driven by data, not headcount, but more staff means more transactions, more documents and more history. When a database approaches the size limit, there may be two ways forward. If the application vendor supports SQL Server 2025, moving to 2025 Express raises the size limit from 10 GB to 50 GB at no licence cost, though the memory and compute caps stay the same. If the database slows because of the memory cap, or the vendor does not support 2025, the move is to a paid edition. Standard edition in SQL Server 2025 is "Limited to lesser of 4 sockets or 32 cores" with a 256 GB buffer pool; SQL Server 2022 Standard is lower, at 24 cores and 128 GB.

Check which edition and version your application uses, how large each database is, and how fast it grew last year.

Remote desktop licensing

If staff work through hosted remote desktop servers, Microsoft states: "Each user and device that connects to a Remote Desktop Services session host or Azure Virtual Desktop session host running Windows Server needs a Remote Desktop Services (RDS) client access license (CAL)". So, where your business licenses remote desktop with CALs, each new person or PC that connects needs one, per user or per device depending on the CAL type you bought; a new starter who never uses remote desktop does not. Where the provider supplies remote desktop under Microsoft's Services Provider License Agreement, the provider licenses it instead: Microsoft states that a "Subscriber Access License (SAL) is required for each unique individual user or device that is authorized to access or otherwise use the licensed products", so growth shows up in the provider's monthly charge rather than as CALs you buy. Ask your provider which applies. Our published articles Per-user or per-device RDS CALs: first establish who licenses the service and Windows Server licensing for hosted virtual machines: cores, minimums and who supplies the licence cover the licence detail.

There are two kinds. Microsoft's comparison shows that per-user licences are "Assigned to a user in Active Directory" and "Can't be tracked within a workgroup". A small office running without a domain hits a design decision here, not just a purchase.

Office plans

Microsoft 365 Business Premium is described as being "For businesses with up to 300 users". A business growing to 60 staff is well inside that; it is not the limit to plan for in this range.

Single points of failure

In our view, for ten staff, one server holding sign-in, files and the application, restored from backup if it fails, may be an acceptable risk. For sixty, an outage stops more people for the same hours. The redesign points are:

  • a second domain controller, so sign-in survives one server failing;
  • separating the database from the remote desktop servers, so one heavy report does not slow everyone's sessions;
  • more than one remote desktop server, so a failure or restart does not stop everyone.

These are design judgements, not product limits; their timing depends on what an hour of downtime costs the business.

What to choose and why

Build the threshold map

Limit What to measure Act when
SQL Server Express database size Each database's size and yearly growth Forecast reaches the limit within the planning period
SQL Server Express memory or compute Slow reports with modest data Application owner confirms the cap is the cause
RDS licences Users and devices connecting Before each hiring wave
Single server for everything Cost of an hour's outage The outage cost justifies a second server

The "act when" column is editorial guidance.

Illustrative example

A 20-person engineering firm plans to reach 45 staff in three years. Its job-costing database runs on SQL Server 2022 Express at 7 GB, growing 1.5 GB a year; the forecast reaches 10 GB in about two years. The firm asks its software vendor first: the vendor supports SQL Server 2025, so the plan is a move to 2025 Express (50 GB limit) in year two, with Standard edition budgeted only if reports slow under the memory cap. The firm buys RDS CALs with each hiring round for the staff who will use remote desktop. It works out that, at around 35 staff, a half-day outage of its single remote desktop server would cost more in lost work than a year of a second server, so it adds the second server then. The example and its figures are illustrative.

Risks and limits

  • Versions change limits. The 2022 and 2025 Express database limits differ; check the version your application supports, not just the newest.
  • Application vendors set their own rules. Some applications support only certain database editions or versions; ask before upgrading.
  • Licensing detail is beyond this article. Edition and remote desktop licensing have further terms; confirm with your licence provider.
  • Growth is not only headcount. An acquisition, a new branch or a document scanning project can hit data limits faster than hiring.

Sources

Opened 15 November 2026; published NetLeverage licensing articles and the Microsoft SPLA programme page opened 16 November 2026.

Related articles: Per-user or per-device RDS CALs: first establish who licenses the service; Windows Server licensing for hosted virtual machines: cores, minimums and who supplies the licence; SQL Server licensing in virtual machines: per-core minimums, Software Assurance and hosting providers.

Related service: Solutions for businesses.

Learning notes

  • SQL Server Express caps compute at 1 socket or 4 cores and buffer pool memory at 1,410 MB.
  • Express database size limit: 10 GB in SQL Server 2022, 50 GB in SQL Server 2025; moving version may be cheaper than moving edition, if the vendor supports it.
  • Where you license remote desktop yourself, each user or device that connects needs an RDS CAL (per user or per device); per-user CALs need Active Directory. Where the provider supplies it under SPLA, it licenses users or devices with SALs instead.
  • Microsoft 365 Business Premium covers up to 300 users.
  • Plan second servers by the cost of an outage, not by a staff number alone.