The following memory and processor requirements apply to all editions of SQL Server:
Component
Requirement
Storage
SQL Server requires a minimum of 6 GB of available hard drive space.
Disk space requirements 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 can apply).
Memory 1
Minimum:
Express Editions: 512 MB
All other editions: 1 GB
Recommended:
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
1 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.
Note
Installation of SQL Server is supported on x64 processors only. It is no longer supported on x86 processors.
Software requirements
The following requirements apply to all installations:
Component
Requirement
Operating system
Windows 10 1607 or greater
Windows Server 2016 or greater.
.NET Framework
SQL Server 2022 (16.x) requires .NET Framework 4.7.2.
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:
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
1,480 MB
Database Engine (as above) with R Services (In-Database)
2,744 MB
Database Engine (as above) with PolyBase Query Service for External Data
4,194 MB
Analysis Services and data files
698 MB
Reporting Services
967 MB
Microsoft R Server (Standalone)
280 MB
Reporting Services - SharePoint
1,203 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 1
27 MB
All features
8,030 MB
1 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. For more information about support for larger sector sizes and manufacturer implementations, see the section "4-KB disk sector sizes" in the white paper SQLIOBasicsCh2.doc. You can download the whitepaper from the Download section of the SQL Server I/O Basics, Chapter 2 article.
If you use advanced format disks that are physically formatted with 4,096 bytes, but expose a logical sector size of 512 bytes, you can read more about the behavior and recommendations in the Tech Community article SQL Server - New drives use 4K sector size.
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 aren't available on the failover target node, the SQL Server resource fails to come online.
SMB storage isn't 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.
Install SQL Server on a domain controller
For security reasons, we recommend that you don't install SQL Server on a domain controller. SQL Server Setup won't block installation on a computer that is a domain controller, but the following limitations apply:
You can't run SQL Server services on a domain controller under a local service account.
After SQL Server is installed on a computer, you can't 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 can't 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 aren't supported where cluster nodes are domain controllers.
SQL Server isn't supported on a read-only domain controller. SQL Server Setup can't create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup fails.
A SQL Server failover cluster instance isn't supported in an environment where only a read-only domain controller is accessible.
Installation media
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 can be slower than running natively because of the overhead of virtualization.
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.