Private SQL Database Server

Now, you don't have to share your SQL database server with other customers.
Host your databases on your own SQL Server and have access to all the server's resources.

Private Microsoft SQL Server

private sql hosting

All our hosting plans includes FREE Shared SQL Databases, but sometimes you need more database power. In these cases, we have our Private SQL Server service.

The Private SQL Server service is essentially your own dedicated virtual server housing SQL server that will only host your SQL databases and no other customer.

The Private SQL server is fully-managed so we will take care of all the server patching and security updates. And, since no other customer will use your Private SQL Server, we can also offer server customization for any special needs you may have.

The Private SQL is still compatible with SQL Management Studio, and it is possible to use the SQL Tools available with our Shared SQL hosting service, like Attach MDF File, Backup Restore and on-demand backups.

Private SQL Features and Pricing

You can choose between SQL 2022, 2019, or SQL 2017 when setting up service.

Private SQL Server A B
CPU Cores 4 8
RAM* 2 GB 2 GB
Disk Space* 200 GB 200 GB
No. Databases No Limit No Limit
Monthly Price $110 $170

* RAM and Disk Space is expandable at any time.

NOTE: Disk Space includes databases, transaction logs, temp directories and backups.

Additional Resources RAM SQL Disk Space**
Monthly Price $25 per GB
(16 GB Max)
$50 per 100 GB
(1000 GB Max)

**NOTE: Once additional SQL Disk Space is added, it cannot be reversed.

Winhost customers can order Private SQL through their Control Panel.

Private SQL vs. Shared SQL

Our Shared Hosting Plans include Shared SQL databases that are hosted on separate SQL servers but shared with many other customer databases. For the vast majority of web applications, the Shared SQL Server is a suitable cost-effective solution.

However, there are use cases where you may consider using a Private SQL Server. These use cases include the following.

  • If you have a mission-critical web application and you want to avoid any database problems due to other customer databases. For example, a "bad neighbor" scenario is possible, where another database on the same server to consume all the shared SQL server resources and slows down your database or makes your database inaccesible. (Winhost cannot vet every application that our customers upload. We do have monitoring on the Shared SQL server and we will do our best to resolve SQL performance issues as quickly as we can.)
  • If you have a very large database.
  • If you host many small databases. For example, a SaaS application may require a database for each user.
  • If you require SQL server customization. For example, SQL Server Agent Jobs, SQL CLR, or insallation of special software.

Any questions about Private SQL Server?