| title | description | author | ms.author | ms.reviewer | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SQL Server 2022: Hardware & software requirements |
A list of hardware, software, and operating system requirements for installing and running SQL Server 2022. |
MikeRayMSFT |
mikeray |
randolphwest, jopilov, rdorr |
11/28/2023 |
sql |
release-landing |
conceptual |
|
[!INCLUDE SQL Server -Windows Only]
The article lists the minimum hardware and software requirements to install and run [!INCLUDE sssql22-md] on the Windows operating system.
For hardware and software requirements for other versions of [!INCLUDE ssNoVersion], see:
The following memory and processor requirements apply to all editions of [!INCLUDE ssnoversion-md]:
| Component | Requirement |
|---|---|
| Storage | [!INCLUDE ssnoversion-md] requires a minimum of 6 GB of available hard drive space. Disk space requirements vary with the [!INCLUDE ssnoversion-md] 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 | [!INCLUDE ssnoversion-md] 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 [!INCLUDE ssDQSServer] component in [!INCLUDE ssDQSnoversion] (DQS) is 2 GB of RAM, which is different from the [!INCLUDE ssnoversion-md] minimum memory requirement. For information about installing DQS, see Install Data Quality Services.
Note
Installation of [!INCLUDE ssnoversion-md] is supported on x64 processors only. It is no longer supported on x86 processors.
The following requirements apply to all installations:
| Component | Requirement |
|---|---|
| Operating system | Windows 10 1607 or greater Windows Server 2016 or greater. |
| .NET Framework | Minimum operating systems include minimum .NET framework. |
| Network Software | Supported operating systems for [!INCLUDE ssnoversion-md] 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. |
[!INCLUDE ssNoVersion] Setup installs the following software components required by the product:
- [!INCLUDE ssNoVersion] Native Client
- [!INCLUDE ssNoVersion] Setup support files
Important
There are additional hardware and software requirements for the PolyBase feature. For more information, see Introducing data virtualization with PolyBase.
The following table shows which editions of [!INCLUDE sssql22-md] are compatible with which versions of Windows:
| [!INCLUDE ssNoVersion] 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 2022 Essentials | 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 |
Installing [!INCLUDE sssql22-md] 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 [!INCLUDE ssNoVersion] on Server Core, see [Install [!INCLUDE ssNoVersion] on Server Core](../../database-engine/install-windows/install-sql-server-on-server-core.md).
For more information about cross-language support and considerations for installing [!INCLUDE ssNoVersion] in localized languages, see [Local Language Versions in [!INCLUDE ssNoVersion]](../../sql-server/install/local-language-versions-in-sql-server.md).
During installation of [!INCLUDE ssnoversion-md], Windows Installer creates temporary files on the system drive. Before you run Setup to install or upgrade [!INCLUDE ssNoVersion], 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 [!INCLUDE ssNoVersion] 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 [!INCLUDE ssnoversion-md] components.
| Feature | Disk space requirement |
|---|---|
| [!INCLUDE ssDE] and data files, Replication, Full-Text Search, and Data Quality Services | 1,480 MB |
| [!INCLUDE ssDE] (as above) with R Services (In-Database) | 2,744 MB |
| [!INCLUDE ssDE] (as above) with PolyBase Query Service for External Data | 4,194 MB |
| [!INCLUDE ssASnoversion] and data files | 698 MB |
| [!INCLUDE ssRSnoversion] | 967 MB |
| [!INCLUDE rsql_platform] (Standalone) | 280 MB |
| [!INCLUDE ssRSnoversion] - SharePoint | 1,203 MB |
| [!INCLUDE ssRSnoversion] Add-in for SharePoint Products | 325 MB |
| [!INCLUDE ssDQSClient] | 121 MB |
| Client Tools Connectivity | 328 MB |
| [!INCLUDE ssISnoversion] | 306 MB |
| Client Components (other than [!INCLUDE ssNoVersion] Books Online components and Integration Services tools) | 445 MB |
| [!INCLUDE ssMDSshort] | 280 MB |
| [!INCLUDE ssNoVersion] 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.
The supported storage types for data files are:
- Local Disk
-
[!INCLUDE ssNoVersion] 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.
Hard disks with sector sizes larger than 4 KB can cause errors when attempting to store SQL Server data files on them. For more information, see Troubleshoot errors related to system disk sector size greater than 4 KB.
-
[!INCLUDE ssNoVersion] failover cluster installation supports Local Disk only for installing the
tempdbfiles. Ensure that the path specified for thetempdbdata and log files is valid on all the cluster nodes. During failover, if thetempdbdirectories aren't available on the failover target node, the [!INCLUDE ssNoVersion] resource fails to come online.
-
- Shared Storage
- Storage Spaces Direct (S2D)
- SMB File Share
- SMB storage isn't supported for [!INCLUDE ssASnoversion] 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 [!INCLUDE ssNoVersion] using SMB file share as a storage option, see [Install [!INCLUDE ssNoVersion] with SMB Fileshare as a Storage Option](../../database-engine/install-windows/install-sql-server-with-smb-fileshare-as-a-storage-option.md).
For security reasons, we recommend that you don't install [!INCLUDE ssnoversion-md] on a domain controller. [!INCLUDE ssNoVersion] Setup won't block installation on a computer that is a domain controller, but the following limitations apply:
- You can't run [!INCLUDE ssNoVersion] services on a domain controller under a local service account.
- After [!INCLUDE ssNoVersion] is installed on a computer, you can't change the computer from a domain member to a domain controller. You must uninstall [!INCLUDE ssNoVersion] before you change the host computer to a domain controller.
- After [!INCLUDE ssNoVersion] is installed on a computer, you can't change the computer from a domain controller to a domain member. You must uninstall [!INCLUDE ssNoVersion] before you change the host computer to a domain member.
- [!INCLUDE ssNoVersion] failover cluster instances aren't supported where cluster nodes are domain controllers.
- [!INCLUDE ssNoVersion] isn't supported on a read-only domain controller. [!INCLUDE ssNoVersion] Setup can't create security groups or provision [!INCLUDE ssNoVersion] service accounts on a read-only domain controller. In this scenario, Setup fails.
- A [!INCLUDE ssNoVersion] failover cluster instance isn't 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 [!INCLUDE ssNoVersion] on a virtual machine can be slower than running natively because of the overhead of virtualization.