Notă
Accesul la această pagină necesită autorizare. Puteți încerca să vă conectați sau să modificați directoarele.
Accesul la această pagină necesită autorizare. Puteți încerca să modificați directoarele.
To plan your use of SQL Server with Dynamics 365 Server, you must understand how Dynamics 365 Customer Engagement (on-premises) uses SQL Server, and what Microsoft Dynamics 365 Server Setup does and does not do:
Dynamics 365 Server requires SQL Server 64-bit versions for storing the databases that contain Dynamics 365 Customer Engagement (on-premises) data and metadata. For specific details, see SQL Server editions.
Reports in Dynamics 365 Customer Engagement (on-premises) depend on 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 Builder, is used to customize reports and write new reports. The Report Designer component is available for download on the Microsoft Download Center and is installed on a workstation, instead of on the computer that is running SQL Server.
Microsoft Dynamics 365 Server Setup does not install SQL Server database engine or SQL Server Reporting Services.
There are many configurations possible based on your expected usage of Dynamics 365 Customer Engagement (on-premises). For information about the feature implications when you install SQL Server Reporting Services on a separate computer, see Editions and Components of SQL Server.
Although we do not recommend it, you can install SQL Server on the same computer as Dynamics 365 Server. 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.
Similarly, we recommend that you install Microsoft Dynamics 365 Reporting Extensions on a separate SQL Server that is running SQL Server Reporting Services. However, if needed you can install Microsoft Dynamics 365 Reporting Extensions on a SQL Server that is running SQL Server Reporting Services but also stores the Dynamics 365 Customer Engagement (on-premises) databases.
Although, in a multiple organization deployment of Dynamics 365 Customer Engagement (on-premises), 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.
Multiple Dynamics 365 Customer Engagement (on-premises) front-end servers that run in a network load balancing cluster can use the same computer that is running SQL Server.
Related sections
Planning deployment of Microsoft Dynamics 365 prerequisites and considerations