On 12 January 2027, Windows Server 2016 reaches the end of extended support. SQL Server 2016 already got there in July 2026. For a lot of Canadian businesses, those dates land on the same machine: an accounting suite, a practice-management system or a custom line-of-business application, running on a server that was specified years ago and has been quietly absorbing more users ever since.
Most of those servers will be moved in the next year or so, and many will move to a hosted environment rather than another box in a back room. That move is the best chance you’ll get to size the server properly. It’s also the moment when the most common mistake happens: copying the old hardware spec, or picking a plan by price, and discovering three months later that month-end reports take twenty minutes.
This guide is about getting the resources right for Windows applications specifically: CPU, memory, storage and network, plus the licensing and compliance questions that shape them. It’s written for owners, office managers and IT generalists choosing Canadian hosting for a Windows workload, not for data centre architects.
Why Windows workloads size differently
If you’ve bought Linux web hosting before, some instincts won’t carry over. Windows application servers differ in four ways that affect sizing.
Licensing is tied to cores. Windows Server and SQL Server are licensed per core in most arrangements. Adding CPU doesn’t just add hardware cost; it can add licence cost, and the two don’t always scale together. That changes which upgrade is cheapest.
The operating system uses more of the machine. A Windows Server installation with the full desktop experience, antivirus, backup agents and management tools has a larger baseline footprint than a minimal Linux server. Microsoft’s published installation minimums (2 GB of RAM for the Desktop Experience and 32 GB of disk) are what it takes to install, not to run a business application comfortably.
Patching means reboots. Microsoft releases security updates on the second Tuesday of each month, and many of them need a restart. Your resource plan needs a maintenance window, and if the application can’t tolerate downtime, it may need a second server.
Many Windows applications are used interactively. Desktop software delivered through Remote Desktop runs every user’s session on the server itself. Ten users means ten copies of the application in memory. That’s a very different load from ten people browsing a website.
Start with measurement, not a spec sheet
The single most useful thing you can do before choosing a plan is measure the server you have now. Windows includes Performance Monitor, which can record counters to a log file for days at a time. Capture at least one full business week, and include a month-end or payroll run if your application has one. Average load tells you very little; the peaks are what users feel.
| Counter | What it tells you | Commonly used warning sign |
| Processor: % Processor Time | How busy the CPUs are | Sustained above 80% during working hours |
| System: Processor Queue Length | Threads waiting for a CPU | Consistently above 2 per core |
| Memory: Available MBytes | Free memory left for the system | Regularly below 10% of installed RAM |
| Memory: Pages/sec | How often memory is swapped to disk | Sustained high values alongside low available memory |
| PhysicalDisk: Avg. Disk sec/Read and sec/Write | Storage latency | Regularly above 20 milliseconds |
| Network Interface: Bytes Total/sec | Network throughput | Approaching the link’s capacity |
Treat those thresholds as rules of thumb rather than hard limits; they’re starting points that experienced administrators use to decide where to look. If your current server shows high disk latency but modest CPU, buying more cores will do nothing for you. If memory is the constraint, storage upgrades won’t help either.
If you’re moving off very old hardware, remember that a modern server core is considerably faster than one from a decade ago. Measured CPU percentage on an old machine overstates what you’ll need on new hardware. Memory and storage needs, by contrast, tend to carry over directly, because data and user counts don’t shrink when the hardware gets faster.
CPU: cores, vCPUs and the licensing multiplier
On hosted servers you’ll usually buy virtual CPUs (vCPUs). A vCPU is a share of a physical processor thread, scheduled by the hypervisor. How much real performance a vCPU represents depends on the processor generation and on how heavily the provider shares physical hardware between customers. Two plans advertising “4 vCPU” can perform quite differently.
A few practical points:
- More cores help only if the application uses them. Many older business applications do most of their work on a single thread. For those, a faster core matters more than more cores. Your vendor can usually tell you.
- SQL Server benefits from parallelism, up to a point. Reporting queries can spread across cores; small transactional workloads often don’t.
- Watch the licensing floor. Microsoft’s per-core licensing models set minimum core counts. Under the programmes many hosts use to license Windows Server monthly, a small virtual machine may be billed for more cores than it actually has. In that case, stepping up from two vCPUs to four or eight can cost far less in licensing than you’d expect. Ask the provider how Windows licensing is calculated on each plan before choosing the smallest one.
- Ask about contention. Dedicated or guaranteed CPU resources avoid the “noisy neighbour” problem, where another customer’s busy period slows your server. For month-end-sensitive workloads, guaranteed resources are worth the premium.
Memory: the resource most often undersized
For Windows business applications, memory is the resource most often undersized, and the one whose shortage hurts most. When Windows runs out of physical memory it starts paging to disk, and everything slows at once.
A sensible way to plan memory is to add up the layers:
- Operating system and agents. Windows itself, antivirus, backup and monitoring tools. Measure this on a clean server; it’s typically several gigabytes once everything is installed.
- The database engine. SQL Server will use as much memory as it’s allowed to, by design, because cached data is faster than data read from disk. Always set its maximum memory, leaving headroom for the operating system and other applications.
- The application itself. Web applications on IIS run in worker processes per application pool; desktop applications delivered by Remote Desktop run once per user session.
- Headroom. At least 20 to 25 percent above measured peak, so a heavy report or an extra user doesn’t tip the server into paging.
The database edition matters here. SQL Server Express, the free edition bundled with many small business applications, is limited to 10 GB per database and about 1.4 GB of memory for its buffer pool in the 2016 to 2022 releases, and to the lesser of one socket or four cores. Microsoft raised some Express and Standard limits in SQL Server 2025. If your database is approaching the Express size limit, or performance is constrained by its memory cap, adding server RAM won’t help until the edition changes. That’s a licensing decision as much as a hardware one.
Storage: latency matters more than capacity
Capacity is easy to estimate: current data, plus growth, plus space for updates and temporary files. Latency is what decides how the application feels.
Business databases make many small, random reads and writes. On spinning disks or overloaded shared storage, each one waits. On modern NVMe solid-state storage, the wait is a fraction of a millisecond. For database-backed Windows applications, the difference between storage tiers is often more noticeable to users than the difference between CPU tiers.
Practical guidance:
- Choose SSD or NVMe storage for anything with a database. Ask what kind of storage the plan uses and whether its performance is guaranteed or shared.
- Separate where it helps. On larger SQL Server installations, placing data files, transaction logs and the tempdb database on separate volumes reduces contention. For small databases, fast storage matters more than separation.
- Budget space for Windows itself. Monthly updates, the component store and log files grow over time. A system drive sized at the bare minimum fills up within a year or two.
- Plan backup storage separately. For many Canadian businesses, financial records must be kept for six years under Canada Revenue Agency rules, which shapes how long backups or archives need to be retained.
Remote Desktop and multi-user applications
If staff use a desktop application through Remote Desktop Services, the server is effectively running everyone’s workstation at once. Sizing becomes a per-user calculation.
The reliable approach is a pilot. Set up the server, have two or three representative users work normally for a day, and measure memory and CPU per session. Then calculate:
Total memory = operating system baseline + (measured memory per session × concurrent users) + 25% headroom
As a worked example with illustrative numbers: if the baseline is 6 GB and each session uses 1.5 GB at peak, twelve concurrent users need 6 + 18 = 24 GB, plus headroom, so roughly 30 GB. The same arithmetic applies to CPU. Your own measurements will differ, especially if users run a browser alongside the application, and that’s exactly why you measure rather than guess.
Two more Remote Desktop considerations:
- Latency is felt directly. Every keystroke and screen update crosses the network. Users notice delay on interactive sessions far more than on websites, which is one of the strongest reasons to host close to them.
- Licensing is per user or device. Remote Desktop access needs its own licences on top of Windows Server. Hosted environments usually provide them as a monthly charge per user.
Licensing on hosted servers
Licensing is where hosted Windows servers differ most from buying your own hardware, and it affects which resources are cost-effective.
Most hosts provide Windows Server under a monthly service-provider licensing programme, which means the licence is included in or added to the plan price. Remote Desktop and SQL Server access are typically billed per user per month under the same arrangement.
If your business already owns Windows Server or SQL Server licences with active Software Assurance or a subscription, Microsoft’s flexible virtualization benefit, introduced in October 2022, generally allows those licences to be used on hardware run by an outsourcing partner, other than a short list of the largest public cloud platforms that Microsoft designates as Listed Providers. A Canadian host outside that list may be able to accept your existing licences, which can change the cost comparison considerably.
Licensing terms are detailed and change periodically. Whichever hosting company in Canada you shortlist, get its licensing position in writing, and check it against your own agreement, before migrating.
Canadian hosting for Windows: where location matters
Server location shapes three things for a Windows workload: how responsive it feels, which laws govern the data, and who answers the phone when something goes wrong.
Responsiveness for interactive users
Websites can hide distance with caching and content delivery networks. Remote Desktop sessions and client-server applications can’t. Every interaction makes a round trip to the server, so a host near your users produces a noticeably smoother experience. For a business with staff in one province, Canadian hosting in a data centre in or near that region keeps those round trips short.
Web hosting in Canada and data residency
Choosing web hosting in Canada for a Windows application server keeps the application, its database and its backups in the country, under Canadian law. For businesses handling client files, payroll or health information, that’s often the deciding factor, and it simplifies the privacy disclosures you’d otherwise need to make about cross-border processing. Canadian hosting also means support and maintenance windows aligned with Canadian business hours, which matters when Windows updates need scheduled reboots.
PIPEDA compliant hosting in Canada for Windows servers
PIPEDA doesn’t require personal information to stay in Canada. It requires organizations to protect personal information with security safeguards appropriate to its sensitivity, and to remain accountable for information handled by third parties such as a hosting provider. Choosing PIPEDA compliant hosting in Canada provides the right foundation; how the Windows server is configured completes the picture.
For hosted Windows servers, the safeguards that matter most are:
- Never expose Remote Desktop directly to the internet. Open RDP ports are among the most heavily attacked services online. Put access behind a VPN or a Remote Desktop Gateway, with multi-factor authentication.
- Encrypt data at rest. Full-volume encryption with BitLocker, plus encrypted backups, protects data if storage is ever removed or mishandled.
- Patch on a schedule. Plan reboots around the monthly update cycle, and don’t run an operating system or database version that no longer receives security updates. That’s the strongest argument for treating the 2016 end-of-support dates as a deadline rather than a suggestion.
- Limit and log access. Separate administrator accounts from daily-use accounts, and keep security logs long enough to investigate an incident.
- Put the hosting agreement in writing. It should state where data and backups are stored, who can access them and how quickly you’ll be told about a security incident.
If a breach of security safeguards creates a real risk of significant harm, PIPEDA requires you to report it to the Office of the Privacy Commissioner, notify the affected individuals and keep a record of every breach for 24 months. A well-configured server makes that much less likely.
Three starting profiles
These are starting points for testing, not prescriptions. Validate any of them with a pilot and your own Performance Monitor data.
| Workload | Reasonable starting point | Scale up when |
| Single business application with a small SQL Server Express database, under 10 users connecting from their own PCs | 4 vCPU, 16 GB RAM, NVMe SSD sized at 3× current data | Database nears the Express size limit, or reports slow at month-end |
| Remote Desktop server for 10 to 15 office users running desktop software | 8 vCPU, RAM calculated from a per-session pilot, NVMe SSD | Available memory falls below 10% at peak, or users report input lag |
| Line-of-business application with SQL Server Standard and 20+ users | Separate application and database servers; database server sized from measured buffer-pool needs | CPU queue builds during business hours, or disk latency rises |
The third row reflects a general principle: once a database becomes central and busy, splitting it onto its own server usually makes both easier to size, patch and troubleshoot.
Common sizing mistakes
- Copying the old server’s specification. It was sized for different hardware and fewer users.
- Sizing for the average. Users experience the peaks: month-end, payroll and the Monday morning login rush.
- Leaving SQL Server’s maximum memory unset, so the database starves the operating system.
- Choosing the cheapest storage tier for a database-heavy application.
- Ignoring the licensing floor, and paying for licences on cores the plan doesn’t use efficiently.
- Skipping the pilot. One day of measured use beats any rule of thumb.
Frequently asked questions
How much RAM does a Windows server need for a business application?
It depends on the operating system baseline, the database engine and how users connect. Microsoft’s installation minimum of 2 GB for the Desktop Experience is far below what a business application needs. Measure your current server’s peak usage, add the database’s memory needs and at least 20 to 25 percent headroom, and size from that result rather than from a generic figure.
Is Canadian hosting a good fit for Windows applications?
Yes, especially for applications that staff use interactively through Remote Desktop or client-server software. Canadian hosting keeps round trips short for users in Canada, keeps data and backups under Canadian law, and aligns support and maintenance windows with Canadian business hours.
What changes when Windows Server 2016 reaches end of support?
After 12 January 2027, Windows Server 2016 no longer receives regular security updates from Microsoft. Running business applications on it increases security risk and makes it harder to demonstrate appropriate safeguards for personal information. Migrating to a supported version is also the right moment to re-measure and resize the server.
What is the best hosting company in Canada for Windows applications?
The best hosting company in Canada for a Windows workload is the one that matches your measured requirements and explains its terms clearly. Look for Canadian data centres, guaranteed CPU and memory, SSD or NVMe storage, transparent Windows and SQL Server licensing, secure remote access options, and support during Canadian business hours.
Can I bring my own Windows Server licences to a hosting provider?
Often, yes. Since October 2022, Microsoft’s flexible virtualization benefit has generally allowed licences with active Software Assurance or subscriptions to run on an outsourcing partner’s hardware, except on Microsoft’s designated Listed Providers. Confirm the details against your own licence agreement and with the hosting provider before migrating.
Conclusion
Choosing server resources for Windows applications isn’t about picking the biggest plan you can afford. It’s about measuring what the application actually does at its busiest, understanding how licensing changes the cost of each resource, and matching memory, storage and CPU to that evidence. Memory and storage latency fix more Windows performance complaints than extra cores do, and a one-day pilot fixes more sizing mistakes than any spreadsheet.
With Windows Server 2016 approaching end of support, many Canadian businesses will make this decision in the next year. Make it once, carefully. Whether you choose a Windows VPS or a dedicated server, web hosting in Canada gives you a practical foundation: choose Canadian hosting that keeps the server close to your users, your data under Canadian law and your support in your own time zone.
Planning a move for your Windows applications?
4GoodHosting provides Canadian hosting on Canadian infrastructure, with server options that can be sized to match your applications and a team that understands Canadian privacy expectations. Talk to us about the resources your Windows workload actually needs.