Windows hosting rarely gets attention until something forces the question. A developer hands over an ASP.NET application. A vendor’s software ships with a SQL Server database. An old site built on Classic ASP needs a new home. Then the questions come quickly. Do I need Windows at all? Which .NET version will the server run? Is “MSSQL included” the same as SQL Server? What does Plesk do that I can’t do myself?
This guide answers those questions for Canadian businesses and the developers who build for them. It is written at a moment when the timing matters more than usual. Microsoft set 10 November 2026 as the end-of-support date for both .NET 8 and .NET 9. SQL Server 2016 left extended support on 14 July 2026. Windows Server 2016, along with the IIS 10 web server that ships with it, follows on 12 January 2027. Three of the main layers in a typical Windows hosting stack hit support deadlines within the same seven months. If you are choosing Windows web hosting in Canada now, the versions a host runs matter as much as the price.
The short answer
- You need Windows hosting for ASP.NET on the .NET Framework (Web Forms, MVC 5, WCF), Classic ASP, and applications tied to Windows-only components. Modern ASP.NET Core runs on Windows or Linux, so for those apps it’s a choice.
- For ASP.NET, target .NET 10, the long-term support release supported to November 2028. Confirm that the host has its runtime installed before you order.
- For MSSQL, ask for the SQL Server version and edition, the database size quota, and whether remote connections are allowed. A backup from a newer SQL Server can’t be restored onto an older one.
- Plesk handles IIS sites, application pools, .NET settings, databases, certificates and Web Deploy publishing, all from a browser, without remote desktop access.
- The Canadian angle comes down to where the database and its backups live, who answers support in your time zone, and how your privacy obligations treat both.
What Windows web hosting actually is
“Windows hosting” describes the operating system on the server, not on your computer. You can manage a Windows-hosted site from a Mac, and a Linux-hosted site from a Windows laptop. What changes is the software stack your application runs on:
- Windows Server, the operating system.
- IIS (Internet Information Services), Microsoft’s web server. It plays the role Apache or Nginx plays on Linux, and it is configured through
web.configfiles rather than.htaccess. - .NET runtimes: the older .NET Framework 4.x, the modern cross-platform .NET (8, 9, 10), or both side by side.
- Microsoft SQL Server (MSSQL), usually alongside MySQL for PHP applications.
- A control panel, almost always Plesk on Windows, since cPanel is Linux-only.
Do you actually need Windows?
That is the first question to settle, because Windows hosting typically costs more than equivalent Linux hosting. Server licensing is part of the price. Use the table below.
| Your application | Windows hosting needed? | Why |
|---|---|---|
| ASP.NET Web Forms, ASP.NET MVC 5, WCF services | Yes | Built on the .NET Framework, which only runs on Windows |
| Classic ASP (.asp pages) | Yes | Runs only on IIS |
| ASP.NET Core (.NET 6 and later) | Optional | Cross-platform. Windows with IIS or Linux both work, so choose by database and team skills |
| Application using MSSQL with Windows authentication or Windows-only features | Usually | SQL Server runs on Linux, but many hosted setups and older apps assume Windows |
| Microsoft Access (.mdb or .accdb) database behind a website | Yes | Access drivers are Windows components |
| WordPress, Drupal, Laravel or other PHP software | No | Built for Linux. Running them on IIS works but adds friction |
If your application is ASP.NET Core with a SQL Server database, both platforms are viable. Teams that already know IIS and Plesk usually stay on Windows. Teams moving to containers often go to Linux. Neither choice is wrong.
ASP.NET hosting in Canada: matching your framework to the server
The single most important compatibility question for ASP.NET hosting in Canada is which .NET your application targets, and whether the host has that runtime installed. There are two families, and they behave differently on a server.
The .NET Framework (4.x)
Web Forms, MVC 5 and older Web API projects target the .NET Framework. Versions 4.8 and 4.8.1 are the end of that line. Microsoft supports them as a component of the Windows release they are installed on, so they stay supported for as long as the server operating system does. Older 4.x versions are being retired on their own schedules: .NET Framework 4.6.2 reaches end of support on 12 January 2027, the same day as Windows Server 2016. An application pinned to 4.6.2 should be retargeted to 4.8 and tested before then. For most code this is a small change. For code with old third-party components, it is the part that needs testing.
Modern .NET (ASP.NET Core)
Modern .NET releases arrive every November. Even-numbered releases are long-term support (LTS) releases with three years of support. Odd-numbered releases are standard-term (STS) releases, which now get 24 months. The current picture looks like this:
| Version | Released | Type | End of support |
|---|---|---|---|
| .NET 6 | November 2021 | LTS | 12 November 2024 (ended) |
| .NET 7 | November 2022 | STS | 14 May 2024 (ended) |
| .NET 8 | 14 November 2023 | LTS | 10 November 2026 |
| .NET 9 | 12 November 2024 | STS | 10 November 2026 |
| .NET 10 | 11 November 2025 | LTS | November 2028 |
| .NET Framework 4.6.2 | 2016 | Framework | 12 January 2027 |
| .NET Framework 4.8 / 4.8.1 | 2019 / 2022 | Framework | Follows the Windows Server version |
An application on an unsupported runtime keeps running, which is what makes the deadline easy to ignore. It just stops receiving security patches. For a public-facing web application, which is exactly what hosting exposes to the internet, that is a real risk. Retargeting to .NET 10 is usually a project-file change (net10.0) followed by a review of breaking changes and a test pass.
How IIS runs ASP.NET Core
IIS doesn’t run ASP.NET Core applications directly. The host installs the .NET Hosting Bundle, which includes the runtime and the ASP.NET Core Module. IIS then hands requests to your application, either inside the IIS worker process (in-process hosting, the default and fastest option) or through a separate process. Three practical consequences follow:
- The host has to install runtimes. On shared hosting you can’t install a runtime yourself, so ask which versions are present and how quickly new ones are added after a release.
- Self-contained deployment is your fallback. You can publish an application with its runtime bundled inside. It still needs the ASP.NET Core Module on the server, but it no longer depends on the host’s installed runtime version. Expect a larger upload, and remember that you are now responsible for patching the runtime you ship.
- Each application should get its own application pool. Pool isolation means a crash or memory leak in one site doesn’t take down another. For ASP.NET Core, the pool’s .NET CLR setting is “No Managed Code,” because the runtime is loaded by the module rather than the classic CLR.
MSSQL hosting in Canada: editions, limits and what “included” means
“MSSQL included” on a plan page usually means you can create one or more databases on a SQL Server instance that the host runs and shares among customers. You get owner rights on your own database, not administrative rights on the server. Good MSSQL hosting in Canada answers five questions clearly.
1. Which version? Version matters for support and for moving data. SQL Server’s lifecycle runs on fixed dates:
| SQL Server version | Mainstream support ended or ends | Extended support ends |
|---|---|---|
| 2016 | July 2021 | 14 July 2026 (ended) |
| 2017 | October 2022 | 12 October 2027 |
| 2019 | 28 February 2025 | 8 January 2030 |
| 2022 | January 2028 | January 2033 |
| 2025 | Current release, generally available since November 2025 | — |
2. Which edition? Edition decides the limits. SQL Server Express is free and is widely used for small applications. Through SQL Server 2022 it caps each database at 10 GB. In SQL Server 2025 the cap rises to 50 GB per database. Both versions limit the buffer pool, the memory SQL Server uses to cache data, to about 1.4 GB, and limit compute to the lesser of one socket or four cores. A host’s shared instance usually runs a commercial edition, but your plan will carry its own database size quota, and that quota is the number to compare.
3. Can you restore your backup? SQL Server backups only restore onto the same or a newer version. A .bak file taken on SQL Server 2022 won’t restore onto a 2019 server. If your development machine runs a newer version than your host, migrate with a scripted export or a BACPAC file instead, or confirm the host’s version first. This single detail derails more first deployments than anything else on the list.
4. Are remote connections allowed? Being able to connect with SQL Server Management Studio or Azure Data Studio from your own machine makes development and troubleshooting far easier. Some hosts open port 1433 to everyone, some allow it by IP address, and some don’t allow it at all. Ask.
5. What isn’t available on shared hosting? Shared database servers normally don’t give customers SQL Server Agent jobs, server-level logins, CLR assemblies or full-text indexing on demand. If your application depends on scheduled jobs inside SQL Server, plan on a VPS.
Two configuration notes save debugging time. First, keep connection strings out of source control and lock them down in web.config or appsettings.json with environment-specific values. Second, recent versions of Microsoft’s SQL client library encrypt connections by default. A connection that fails with a certificate error after a library upgrade is usually that change, and it should be fixed with a trusted certificate rather than by switching encryption off.
Plesk Windows hosting: what the control panel does for you
On a Windows server, Plesk is the layer between you and IIS. Plesk Windows hosting matters because, without it, nearly everything below would require remote desktop access to the server, which shared hosting doesn’t provide.
From a Plesk subscription you can typically:
- Create sites and subdomains, each with its own document root and IIS application pool.
- Choose ASP.NET and .NET settings per site, and manage
web.configoptions such as default documents, MIME types and error pages. - Set up URL Rewrite rules (the IIS equivalent of Apache’s rewrite rules) and redirects.
- Create MSSQL and MySQL databases and their users, and note the connection details.
- Enable Web Deploy publishing, so Visual Studio or a build pipeline can publish directly to the site.
- Install TLS certificates, manage FTP accounts and the file manager, run scheduled tasks, read IIS logs, and restore from backups.
A typical first deployment through Plesk
- Create the database and a database user in Plesk. Record the server name, database name and credentials.
- Put the production connection string in your configuration, not in code.
- If the application targets ASP.NET Core, confirm in Plesk that the site’s application pool uses “No Managed Code.” For the .NET Framework, select the 4.x version.
- Enable Web Deploy for the site and download the publishing settings, or use FTP if your workflow prefers it.
- Publish from Visual Studio or with
dotnet publish. Choose a self-contained deployment if the host lacks your runtime. - Create the database schema with your migration scripts, or import a BACPAC or script that matches the server version.
- Install a certificate, force HTTPS, then test the full flow end to end: login, forms, email sending and error pages.
What Plesk can’t do on shared hosting
Plesk exposes what the host allows. It won’t let you install Windows services, register COM components, change server-wide IIS modules, add a .NET runtime, or run long-lived background processes outside your application. If your application needs any of those, the honest answer is a Windows VPS with remote desktop access.
Shared Windows hosting or a Windows VPS?
| Situation | Shared Windows hosting | Windows VPS |
|---|---|---|
| A business site or a small ASP.NET application | Good fit | Usually more than you need |
| Database within the plan’s quota, no SQL Agent jobs | Good fit | — |
| Need a .NET runtime the host doesn’t offer | Use self-contained deployment | Install it yourself |
| Background services, scheduled jobs in SQL Server, COM components | Not possible | Required |
| Remote desktop access, custom IIS modules, server-level settings | Not possible | Required |
| Several client sites managed by an agency | Possible on larger plans | Often simpler, with full control |
| Predictable heavy traffic or large databases | Outgrown | Size CPU and RAM to the workload |
If you are weighing a VPS, the sizing questions (CPU, memory for SQL Server, storage latency and Windows licensing) are a separate exercise covered in our guide to Windows VPS hosting options.
The Canadian angle: privacy, latency and support
Most of the decisions above are technical. Three considerations are specific to running Windows web hosting in Canada.
Where your data sits. On a typical ASP.NET site, the SQL Server database is where the personal information lives: customer accounts, orders, form submissions. PIPEDA doesn’t require that data to stay in Canada, but it makes you accountable for it wherever it goes, and it expects you to tell people when it is processed elsewhere. Businesses with customers in Québec must assess the risks before personal information leaves the province, including when it goes to another province. A host whose web servers, database servers and backups are all in Canada keeps that part of your documentation short. Ask specifically where database backups are stored, because they are copies of everything.
Latency. A site served from Vancouver or Toronto usually responds faster to Canadian visitors than one served from overseas, simply because the network path is shorter. For database-backed ASP.NET pages, where every request may involve several queries, keeping the web server and the SQL Server close together matters even more than the distance to the visitor.
Support hours. Deployment problems on Windows often show up at awkward moments: a failed publish at 6 p.m., or an application pool that keeps recycling the morning after a release. Support staffed in Canadian time zones, by people who know IIS and SQL Server, is worth asking about directly.
4GoodHosting’s Windows web hosting plans run on IIS with the Plesk control panel, include nightly backups, and are hosted on Canadian infrastructure in Vancouver and Toronto. The plan page asks customers to confirm their ASP.NET runtime and SQL Server requirements with support before ordering. That is the right habit with any host, and it is exactly what the checklist below is for.
Before you order: ten questions for any Windows host
- Which Windows Server version runs the shared servers, and when does it reach end of support?
- Which .NET runtimes are installed, and is .NET 10 among them?
- How soon after a new .NET release are new runtimes added?
- Which .NET Framework versions are available, and is 4.8 the default?
- Is MSSQL included on this plan? If so, which version, edition and database size quota?
- Are remote SQL Server connections allowed, and from where?
- Is Web Deploy publishing enabled, or is FTP the only deployment route?
- Does each site get its own application pool?
- Where are the web servers, database servers and backups physically located, and how long are backups kept?
- Is a TLS certificate included, and who renews it?
Get the answers in writing. They double as the hosting section of your privacy documentation and as the baseline for your next upgrade.
The 2026–2027 upgrade calendar
| Date | What ends | What to do |
|---|---|---|
| 14 July 2026 (passed) | SQL Server 2016 extended support | Move databases to a supported version, or confirm your host has |
| 10 November 2026 | .NET 8 and .NET 9 support | Retarget applications to .NET 10 and confirm the host runs it |
| 12 January 2027 | Windows Server 2016, IIS 10 on Windows Server 2016, .NET Framework 4.6.2 | Confirm your host’s server version. Retarget 4.6.2 apps to 4.8 |
| 12 October 2027 | SQL Server 2017 extended support | Plan database moves early, because restores only go forward |
| November 2028 | .NET 10 support | Plan the next LTS move in 2028 |
Frequently asked questions
What is Windows web hosting?
Windows web hosting is hosting on servers that run Windows Server and Microsoft’s IIS web server, usually with .NET runtimes, Microsoft SQL Server and the Plesk control panel. You need it for applications built on the .NET Framework, such as ASP.NET Web Forms and MVC 5, and for Classic ASP. Modern ASP.NET Core applications can run on Windows or Linux.
Do I need Windows hosting for ASP.NET Core?
No. ASP.NET Core is cross-platform and runs on Linux or Windows. Windows hosting with IIS and Plesk is a good choice if your team already works with IIS, uses SQL Server features tied to Windows, or wants to manage sites through Plesk. Linux suits teams moving toward containers.
Which .NET version should I target in 2026?
Target .NET 10. It is the current long-term support release, released on 11 November 2025 and supported until November 2028. Microsoft set 10 November 2026 as the end-of-support date for both .NET 8 and .NET 9. Before deploying, confirm that your host has the .NET 10 runtime installed, or publish your application as self-contained.
What is the size limit for SQL Server Express?
SQL Server Express limits each database to 10 GB in SQL Server 2022 and earlier, and to 50 GB in SQL Server 2025. In both versions it uses about 1.4 GB of memory for its data cache and the lesser of one socket or four cores. On shared hosting, the plan’s own database quota is usually the limit that matters.
Can I restore my SQL Server backup on any host?
Only if the host runs the same or a newer SQL Server version than the one that created the backup. A backup from SQL Server 2022 won’t restore onto SQL Server 2019. If the versions don’t match, move the database with a BACPAC file or generated scripts, or ask the host which version it runs before you migrate.
What does Plesk do on Windows hosting?
Plesk lets you manage IIS websites from a browser. You can create sites and application pools, choose ASP.NET settings, create MSSQL and MySQL databases, set up URL Rewrite rules, enable Web Deploy publishing from Visual Studio, install TLS certificates and restore backups, all without remote desktop access. It can’t install server software such as new .NET runtimes or Windows services.
When should I move from shared Windows hosting to a Windows VPS?
Move to a Windows VPS when your application needs things shared hosting can’t provide. These include background Windows services, SQL Server Agent jobs, COM components, custom IIS modules, a runtime the host doesn’t offer, remote desktop access, or more CPU and memory than a shared plan allows.
Does hosting my ASP.NET site in Canada matter?
It can. A server in Canada usually responds faster to Canadian visitors, and keeping the web server, SQL Server database and backups in Canada simplifies your privacy documentation. PIPEDA doesn’t require Canadian hosting, but it makes you accountable for personal information wherever it is processed. Québec also requires a risk assessment before personal information leaves the province.
Key takeaways
- Windows hosting is required for .NET Framework applications (Web Forms, MVC 5, WCF) and Classic ASP. ASP.NET Core can run on either platform.
- Microsoft set 10 November 2026 as the end of support for .NET 8 and .NET 9. Target .NET 10, the LTS release supported to November 2028.
- Windows Server 2016, IIS 10 on it, and .NET Framework 4.6.2 all reach end of support on 12 January 2027.
- On shared hosting, the host installs runtimes. Self-contained deployment is the fallback when your version isn’t there yet.
- For MSSQL hosting in Canada, ask for the version, edition, database quota and remote-access policy. Backups only restore onto the same or a newer version.
- SQL Server Express databases are capped at 10 GB through 2022 and 50 GB in 2025, with about 1.4 GB of memory for caching.
- Plesk handles IIS sites, application pools, databases, certificates and Web Deploy publishing, but can’t install server-level software.
- Background services, SQL Agent jobs, COM components or remote desktop access mean a Windows VPS.
- In Canada, ask where the database and its backups live. They are where your customers’ personal information sits.
Conclusion
Windows hosting is a narrower decision than it looks once you separate the layers. The operating system and IIS determine what can run at all. The installed .NET runtimes decide whether your application starts. The SQL Server version and edition decide whether your data fits and whether your backups restore. Plesk decides how much of this you can manage without asking support. Between July 2026 and January 2027, several of those layers are passing support deadlines, so the questions to ask about Windows web hosting in Canada are sharper than usual: which versions, which limits, and where everything is stored.
Ask those questions before you order, get the answers in writing, and target supported versions from the first deployment. That way your Windows application will spend its time serving customers rather than waiting for an upgrade.
Ready to move your ASP.NET or MSSQL application?
If you’re moving an ASP.NET or MSSQL application, start with the questions in this guide. 4GoodHosting’s team will confirm runtime and SQL Server requirements for your application before you order, and our Windows plans run on Plesk with nightly backups on Canadian infrastructure.
Compare Windows web hosting in Canada with Plesk and nightly backups →