Sdílet prostřednictvím

SQL Server installation and configuration

  • Článek

 

Applies To: Dynamics CRM 2013

To plan your use of Microsoft SQL Server with Microsoft Dynamics CRM Server, you must understand how Microsoft Dynamics CRM uses SQL Server, and what Microsoft Dynamics CRM Server Setup does and does not do:

  • Microsoft Dynamics CRM Server requires SQL Server 64-bit versions for storing the databases that contain Microsoft Dynamics CRM data and metadata. For specific details, see SQL Server editions (database engine) in this guide.

  • Reports in Microsoft Dynamics CRM depend on Microsoft SQL Server Reporting Services, a feature in SQL Server. Reporting Services includes two server components that are used to store, display, and manage reports: Report Server and Report Manager. A third component, Report Designer, is used to customize reports and write new reports. The Report Designer component is available with Microsoft Visual Studio and is typically installed on a workstation, instead of on the computer that is running SQL Server.

  • Microsoft Dynamics CRM Server Setup does not install SQL Server database engine or Microsoft SQL Server Reporting Services.

There are many configurations possible based on your expected usage of Microsoft Dynamics CRM. For information about the licensing implications when you install Microsoft SQL Server Reporting Services on a separate computer, see SQL Server 2008 R2 Licensing.

  • Although we do not recommend it, you can install SQL Server on the same computer as Microsoft Dynamics CRM Server 2013. For better performance, install and run SQL Server on a separate dedicated computer. For better performance and improved availability, install and run SQL Server on separate multiple dedicated computers in a clustered configuration. For more information, see Set configuration and organization databases for SQL Server 2012 AlwaysOn failover.

  • Similarly, we recommend that you install Microsoft Dynamics CRM Reporting Extensions on a separate SQL Server that is running Microsoft SQL Server Reporting Services. However, if needed you can install Microsoft Dynamics CRM Reporting Extensions on a SQL Server that is running Microsoft SQL Server Reporting Services but also stores the Microsoft Dynamics CRM databases.

    Notice that, when you run the database engine and Reporting Services on separate SQL Servers, the versions of SQL Server do not have to match. For example, the SQL Server database engine where the Microsoft Dynamics CRM databases are stored can be Microsoft SQL Server 2008 R2 and the Reporting Services server where the Microsoft Dynamics CRM Reporting Extensions are installed can be Microsoft SQL Server 2012.

  • Although, in a multiple organization deployment of Microsoft Dynamics CRM, you can specify different Reporting Services servers or server instances when you create or edit an organization, only one instance of Reporting Services is supported for all organizations in the deployment. For better load balancing of reports, we recommend configuring Report Server in a Network Load Balancing (NLB) cluster. For more information, see Configure a Report Server on a Network Load Balancing Cluster.

  • Multiple Microsoft Dynamics CRM front-end servers that run in a network load balancing cluster can use the same computer that is running SQL Server. For more information, see Install Microsoft Dynamics CRM Server 2013 on multiple computers.

In This Section

SQL Server requirements and recommendations for Microsoft Dynamics CRM

SQL Server deployment

Additional resources for SQL Server

Prerequisites and considerations for planning your deployment of Microsoft Dynamics CRM 2013

Planning requirements for Microsoft SQL Server Reporting Services

© 2016 Microsoft Corporation. All rights reserved. Copyright