SQL Server 2019: Hardware and software requirements
Applies to: SQL Server (all supported versions) - Windows only
The article lists the minimum hardware and software requirements to install and run SQL Server 2019 (15.x) on the Windows operating system.
For hardware and software requirements for other versions of SQL Server , see:
The following memory and processor requirements apply to all editions of SQL Server:
|Hard Disk||SQL Server requires a minimum of 6 GB of available hard-disk space.
Disk space requirements will vary with the SQL Server components you install. For more information, see Hard Disk Space Requirements later in this article. For information on supported storage types for data files, see Storage Types for Data Files.
|Monitor||SQL Server requires Super-VGA (800x600) or higher resolution monitor.|
|Internet||Internet functionality requires Internet access (fees may apply).|
Express Editions: 512 MB
All other editions: 1 GB
Express Editions: 1 GB
All other editions: At least 4 GB and should be increased as database size increases to ensure optimal performance.
|Processor Speed||Minimum: x64 Processor: 1.4 GHz
Recommended: 2.0 GHz or faster
|Processor Type||x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support|
Installation of SQL Server is supported on x64 processors only. It is no longer supported on x86 processors.
* The minimum memory required for installing the Data Quality Server component in Data Quality Services (DQS) is 2 GB of RAM, which is different from the SQL Server minimum memory requirement. For information about installing DQS, see Install Data Quality Services.
The following requirements apply to all installations:
|Operating system||Windows 10 TH1 1507 or greater
Windows Server 2016 or greater
|.NET Framework||Minimum operating systems includes minimum .NET framework.|
|Network Software||Supported operating systems for SQL Server have built-in network software. Named and default instances of a stand-alone installation support the following network protocols: Shared memory, Named Pipes, and TCP/IP.
SQL Server Setup installs the following software components required by the product:
- SQL Server Native Client
- SQL Server Setup support files
There are additional hardware and software requirements for the PolyBase feature. For more information, see Get started with PolyBase.
Operating system support
The following table shows which editions of SQL Server 2019 (15.x) are compatible with which versions of Windows:
|SQL Server edition:||Enterprise||Developer||Standard||Web||Express|
|Windows Server 2022 Datacenter||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2022 Datacenter: Azure Edition||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2022 Standard||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2019 Datacenter||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2019 Standard||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2019 Essentials||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2016 Datacenter||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2016 Standard||Yes||Yes||Yes||Yes||Yes|
|Windows Server 2016 Essentials||Yes||Yes||Yes||Yes||Yes|
|Windows 11 IoT Enterprise||No||Yes||Yes||No||Yes|
|Windows 11 Enterprise||No||Yes||Yes||No||Yes|
|Windows 11 Professional||No||Yes||Yes||No||Yes|
|Windows 11 Home||No||Yes||Yes||No||Yes|
|Windows 10 IoT Enterprise||No||Yes||Yes||No||Yes|
|Windows 10 Enterprise||No||Yes||Yes||No||Yes|
|Windows 10 Professional||No||Yes||Yes||No||Yes|
|Windows 10 Home||No||Yes||Yes||No||Yes|
Server core support
Installing SQL Server 2019 (15.x) on Server Core mode is supported by the following editions of Windows Server:
Windows Server 2022 Core
Windows Server 2019 Core
Windows Server 2016 Core
For more information on installing SQL Server on Server Core, see Install SQL Server on Server Core.
For more information about cross-language support and considerations for installing SQL Server in localized languages, see Local Language Versions in SQL Server .
Disk space requirements
During installation of SQL Server, Windows Installer creates temporary files on the system drive. Before you run Setup to install or upgrade SQL Server, verify that you have at least 6.0 GB of available disk space on the system drive for these files. This requirement applies even if you install SQL Server components to a non-default drive.
Actual hard disk space requirements depend on your system configuration and the features that you decide to install. The following table provides disk space requirements for SQL Server components.
|Feature||Disk space requirement|
|Database Engine and data files, Replication, Full-Text Search, and Data Quality Services||1480 MB|
|Database Engine (as above) with R Services (In-Database)||2744 MB|
|Database Engine (as above) with PolyBase Query Service for External Data||4194 MB|
|Analysis Services and data files||698 MB|
|Reporting Services||967 MB|
|Microsoft R Server (Standalone)||280 MB|
|Reporting Services - SharePoint||1203 MB|
|Reporting Services Add-in for SharePoint Products||325 MB|
|Data Quality Client||121 MB|
|Client Tools Connectivity||328 MB|
|Integration Services||306 MB|
|Client Components (other than SQL Server Books Online components and Integration Services tools)||445 MB|
|Master Data Services||280 MB|
|SQL Server Books Online Components to view and manage help content*||27 MB|
|All Features||8030 MB|
*The disk space requirement for downloaded Books Online content is 200 MB.
Storage types for data files
The supported storage types for data files are:
- Local Disk
- SQL Server currently supports disk drives that have standard native sector sizes of 512 bytes and 4 KB. Hard disks with sector sizes larger than 4 KB may cause errors when attempting to store SQL Server data files on them. See Hard disk drive sector-size support boundaries in SQL Server for more information on hard disk sector-size support in SQL Server. For more information, see Troubleshoot errors related to system disk sector size greater than 4 KB.
- SQL Server failover cluster installation supports Local Disk only for installing the tempdb files. Ensure that the path specified for the tempdb data and log files is valid on all the cluster nodes. During failover, if the tempdb directories are not available on the failover target node, the SQL Server resource will fail to come online.
- Shared Storage
- Storage Spaces Direct (S2D)
- SMB File Share
- SMB storage is not supported for Analysis Services data files for either standalone or clustered installations. Use direct attached storage, a storage area network, or S2D instead.
- SMB storage can be hosted by a Windows File Server or a third-party SMB storage device. If Windows File Server is used, the Windows File Server version should be 2008 or later. For more information about installing SQL Server using SMB file share as a storage option, see Install SQL Server with SMB Fileshare as a Storage Option.
Installing SQL Server on a domain controller
For security reasons, we recommend that you do not install SQL Server on a domain controller. SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:
- You cannot run SQL Server services on a domain controller under a local service account.
- After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
- After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
- SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
- SQL Server is not supported on a read-only domain controller. SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
- A SQL Server failover cluster instance is not supported in an environment where only a read-only domain controller is accessible.
You can get relevant installation media from the following locations:
Alternatively, you can create an Azure virtual machine already running SQL Server though SQL Server on a virtual machine will be slower than running natively because of the overhead of virtualization.
Submit and view feedback for