sql-server-requirements-recommendations.md

title	description	ms.custom	ms.date	ms.reviewer	ms.suite	ms.tgt_pltfrm	ms.topic	applies_to	ms.assetid	caps.latest.revision	author	ms.author
SQL Server requirements and recommendations for Dynamics 365 Customer Engagement (on-premises) | Microsoft Docs	Learn about the requirements and recommendations for your SQL Server deployment when used with Dynamics 365 Customer Engagement (on-premises)		10/01/2018				article	Dynamics 365 (on-premises)	be02a7d8-d0a6-44b2-8e45-7216bb7045e5	26	Mattp123	matp

SQL Server requirements and recommendations for Microsoft Dynamics 365 Customer Engagement (on-premises)

The following requirements and recommendations apply to new and existing installations of [!INCLUDEpn_SQL_Server_short].

General requirements and recommendations

• [!INCLUDEpn_microsoftcrm_server] requires an instance of [!INCLUDEpn_SQL_Server_Reporting] be installed, running, and available. All installations of the supported [!INCLUDEpn_SQL_Server_short] editions can be used as the reporting server. However, the [!INCLUDEpn_reporting_services_short] edition must match the [!INCLUDEpn_SQL_Server_short] edition.

• For a list of supported [!INCLUDEpn_SQL_Server_short] editions, see SQL Server editions.

• When [!INCLUDEpn_microsoftcrm_server] and [!INCLUDEpn_SQL_Server_short] are installed on different computers, they must be in the same [!INCLUDEpn_Active_Directory] domain.

• [!INCLUDEpn_microsoftcrm_server] Setup, Dynamics 365 Customer Engagement (on-premises) PowerShell cmdlets, and [!INCLUDEpn_deploymentmanager] support the default instance or a named instance of [!INCLUDEpn_SQL_Server_short].

• Although you can install [!INCLUDEpn_SQL_Server_short] by using either [!INCLUDEpn_Windows_Authentication] or mixed-mode authentication, [!INCLUDEpn_Windows_Authentication] is a prerequisite for [!INCLUDEpn_microsoftcrm].

• The service account that [!INCLUDEpn_SQL_Server_short] uses to log on to the network must be either a domain user account (recommended) or the Network Service account (you can’t use a local user account on the server). Using a low-privilege account strategy is recommended to help avoid compromising the security of the server.

• The [!INCLUDEpn_SQL_Server_short] service must be started. This service should be configured to automatically start when the computer is started.

• [!INCLUDEpn_SQL_Server_Agent] must be started. This service should be configured to automatically start when the computer is started.

• [!INCLUDEpn_SQL_Server_short] Full-Text Search must be installed and started. This service should be configured to automatically start when the computer is started.

• [!INCLUDEpn_microsoftcrm_server] Setup requires a network library to authenticate [!INCLUDEpn_SQL_Server_short]. By default, [!INCLUDEpn_TCP/IP] network libraries are enabled when you install [!INCLUDEpn_MS_SQL_Server]. [!INCLUDEpn_SQL_Server_short] can use both [!INCLUDEpn_TCP/IP] or Named Pipes for authentication. However, the computer that is running [!INCLUDEpn_SQL_Server_short] must be configured for at least one of the two network libraries.

• We recommend that the computer that is running [!INCLUDEpn_SQL_Server_short] be located on the same local area network (LAN) as the computer that is running the [!INCLUDEpn_microsoftcrm_server] [!INCLUDEBack_End_Server] roles.

• The computer that is running [!INCLUDEpn_SQL_Server_short] must be configured to have sufficient disk space, memory, and processing power to support the [!INCLUDEpn_microsoftcrm] environment. For more information, see Microsoft Dynamics 365 Server hardware requirements.

• Although it’s optional, consider accepting the [!INCLUDEpn_SQL_Server_short] default settings for Collation Designator, Sort Order, and SQL Collation. [!INCLUDEpn_microsoftcrm] supports the following collation orders:

  • Case-sensitive

  • Case-insensitive

  • Accent-sensitive

  • Accent-insensitive

  • Binary sort order (such as Latin1_General_100_BIN)

  [!NOTE] [!INCLUDEpn_microsoftcrm] sets the collation order at the database level. This setting might differ from that set at the [!INCLUDEpn_SQL_Server_short] level.

• Review all [!INCLUDEpn_SQL_Server_short] installation options and be prepared to make the needed selections when you run Setup. For more information, see SQL Server Installation.

• If you plan to install [!INCLUDEpn_SQL_Server_short] in a location other than the default file location, see File Locations for Default and Named Instances of SQL Server.

  You should also consider where the [!INCLUDEpn_microsoftcrm] databases are located on the server, and the hard-disk configuration that will support them.

  [!NOTE] To achieve the best combination of disk fault tolerance and performance, consider the many specifications for redundant array of independent disks (RAID) available from hardware vendors. Format the disks where the [!INCLUDEpn_SQL_Server_short] database files reside for the fault-tolerance requirements of the application and performance parameters for the I/O activity occurring on that partition.

• We recommend that common language runtime (CLR) be enabled on the [!INCLUDEpn_SQL_Server_short] that hosts the [!INCLUDEpn_microsoftcrm] organization database. CLR can show a significant improvement in performance for some features such as time zone conversions when you run dashboards, charts, advanced finds, and [!INCLUDEpn_microsoftcrm] interactive service hub experience. [!INCLUDEproc_more_information] CLR Integration - Enabling

See also

Microsoft SQL Server hardware requirements for Microsoft Dynamics 365 Server

[!INCLUDEfooter-include]