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.

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.

Recommended: 2.0 GHz or faster

Windows Server 2016 or greater

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:

Server core support

Installing SQL Server 2019 (15.x) on Server Core mode is supported by the following editions of Windows Server:

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.

Cross-language support

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.

*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
  • 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.

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 will be slower than running natively because of the overhead of virtualization.

Next steps

Once you’ve reviewed the hardware and software requirements for installing SQL Server , you can start to Plan a SQL Server Installation or review the Security considerations for SQL Server .

Supported version & edition upgrades (SQL Server 2019)

Applies to: SQL Server (all supported versions) — Windows only

You can upgrade from SQL Server 2012 (11.x), SQL Server 2014 (12.x), SQL Server 2016 (13.x), and SQL Server 2017 (14.x). This article lists the supported upgrade paths from these SQL Server versions, and the supported edition upgrades for SQL Server 2019 (15.x).

Pre upgrade Checklist

• Before upgrading from one edition of SQL Server 2019 (15.x) to another, verify that the functionality you are currently using is supported in the edition to which you are moving.
• Verify supported hardware and software.
• Before upgrading SQL Server, enable Windows Authentication for SQL Server Agent and verify the default configuration: that the SQL Server Agent service account is a member of the SQL Server sysadmin group.
• To upgrade to SQL Server 2019 (15.x), you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server.
• Upgrade will be blocked if there is a pending restart.
• Upgrade will be blocked if the Windows Installer service is not running.

Unsupported Scenarios

Cross-version instances of SQL Server 2019 (15.x) are not supported. Version numbers of the Database Engine components must be the same in an instance of SQL Server 2019 (15.x).

SQL Server 2019 (15.x) is only available for 64-bit platforms. Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of SQL Server to native 64-bit using SQL Server Setup. However, you can back up or detach databases from a 32-bit instance of SQL Server, and then restore or attach them to a new instance of SQL Server (64-bit) if the databases are not published in replication. You must re-create any logins and other user objects in master, msdb, and model system databases.

You cannot add new features during the upgrade of your existing instance of SQL Server. After you upgrade an instance of SQL Server to SQL Server 2019 (15.x), you can add features by using the SQL Server 2019 (15.x) Setup. For more information, see Add Features to an Instance of SQL Server (Setup).

Upgrades from Earlier Versions to SQL Server 2019 (15.x)

SQL Server 2019 (15.x) supports upgrade from the following versions of SQL Server:

• SQL Server 2012 (11.x) SP4 or later
• SQL Server 2014 (12.x) SP3 or later
• SQL Server 2016 (13.x) SP2 or later
• SQL Server 2017 (14.x)

The table below lists the supported upgrade scenarios from earlier versions of SQL Server to SQL Server 2019 (15.x).

* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Early Adopter Program.

Migrate to SQL Server 2019

You can migrate databases from older versions. For example, you can migrate databases from SQL Server 2008 R2 to SQL Server 2019.

The following tips and tools can help you plan and implement your migration.

Migration tools: Migration is supported through Data Migration Assistant (DMA).

Backup and restore: A backup taken on SQL Server 2008 or SQL Server 2008 R2 can be restored to SQL Server 2019.

Log shipping: Log shipping is supported if primary is running SQL Server 2008 SP3 or later, or SQL Server 2008 R2 SP2 or later, and secondary is running SQL Server 2019.

If an automatic or manual failover happens and the SQL Server 2019 instance becomes primary, SQL Server 2008 or SQL Server 2008 R2 instance becomes secondary and cannot receive changes from primary.

Bulk load: Tables can be bulk copied from SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2019.

SQL Server 2019 (15.x) Edition Upgrade

The following table lists the supported edition upgrade scenarios in SQL Server 2019 (15.x).

For step-by-step instructions on how to perform an edition upgrade, see Upgrade to a Different Edition of SQL Server (Setup).

Additionally you can also perform an edition upgrade between SQL Server 2019 (15.x) Enterprise (Server+CAL license) and SQL Server 2019 (15.x) Enterprise (Core License):

* Also applies to SQL Server 2019 (15.x) Express with Tools and SQL Server 2019 (15.x) Express with Advanced Services.

** Changing the edition of a clustered instance of SQL Server 2019 (15.x) limited. The following scenarios are not supported for SQL Server 2019 (15.x) failover clusters:

SQL Server 2019 (15.x) Enterprise to SQL Server 2019 (15.x) Developer, Standard, or Evaluation.

SQL Server 2019 (15.x) Developer to SQL Server 2019 (15.x) Standard or Evaluation.

SQL Server 2019 (15.x) Standard to SQL Server 2019 (15.x) Evaluation.

SQL Server 2019 (15.x) Evaluation to SQL Server 2019 (15.x) Standard.

Вам также может понравиться

Windows или Linux: Что лучше выбрать?

Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux

Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux

Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux

ИТ База знаний Курс по Asterisk Полезно — Узнать IP —