MS Dynamics CRM 2016 with SQL 2014 Install and Configuration
Welcome to my first series of posts on setting up Microsoft Dynamics CRM with SQL Server 2014.
This is something I have done from Installation, configuration and testing so please feel free to ask any questions in the comments below. I have kept it simple by being brief with the steps and hope the screenshots help with explaining the process.
This setup was done for testing and was all performed on one server. It was a CRM full server setup with Integrated SQL 2014 Developer edition installed on the same box and setup as a member server as part of a Windows domain with Active Directory authentication.
This first part will focus on setting up the SQL server including Windows Server Installation.
Windows Server Installation and setup
- Install Windows, Windows 2012 or above is supported. Windows 2008 R2 and below are not.
- Use recommended hardware specification as noted in CRM 2016 Planning and Deployment guide.
- Recommended to set static IP Addressing
- Provide host name in Windows and join to domain
- Install Windows updates
- Mounted SQL 2014 ISO. Installation and click ‘New SQL server stand-alone installation or add features to an existing installation’.
- Choose Product edition
- Accept License Terms
- The SQL setup will then perform a series of pre-requisite installation rules. Ensure there are no errors at this point otherwise you may not be able to continue.
- Minimum recommendation is to choose the options as shown below. Here you can also choose the installation path, my recommendation is to keep application data on a separate partition and/or drive, that is shown here:
- If the server is a brand new Windows 2012 server without any added roles or features, you may find you need to install .Net Framework 3.5 using Add features in Server Manager.
- If you already have the .Net framework installed, you will be able to proceed to the next step. Provide a naming instance ID for the SQL server. This will then install the necessary instance in the location specified earlier in the steps.
- Provide a separate service account, this is recommended or you can use the local service accounts built in on the server which is fine for test/dev purposes.
- Choose authentication mode, I chose Mixed mode so I have two routes of authentication. Supply a password for the ‘SA’ account and specify any specific SQL server administrators either locally on the server or within Active Directory.
- Check the installation paths to ensure the stored directories are correct, you can amend if necessary. I left these as they are.
- CRM requires Reporting services, choose the install and configure option.
- SQL will then ask you to verify with the settings before installation begins.
- Once installed you should see a complete page. It is recommended to perform a Windows Update to ensure SQL is patched according to Microsoft updates.
The next post will focus on a full server CRM Dynamics 2016 Installation.