You’re offline. This is a read only version of the page.
Does anyone know if Microsoft even plans to test SQL Server 2019 compatibility with Dynamics 365 8.0, 9.0 (On-premises)?
Couple questions 1) So did you end up having to have both SQL Server 2017 just for SSRS and SQL Server 2019 for CRM? 2) Do you know if CRM will still be supported by Microsoft if it is running on a SQL version they do not technically support?
Aye, we’ve upgraded Live now to 2019 and works very smoothly.
The main upgrade from SQL 2016 was done as a in-place upgrade and worked without impacting Dynamics.
SSRS is a bit of a faff as needs a bit of time to reinstall and then fudge the Data Connector in - but with the steps above, it works grand for reporting.
The next step for us is to enable Encryption at Rest TDE as this is a standard feature in 2019. (whereas was previously a Enterprise Only feature in earlier SQL versions)
After spending a few hours I've figured out what exactly should I do to install this glorious SSRS CRM Data Connector (Microsoft Dynamics CRM Reporting Extensions) on SQL Server 2017.
These Extensions were for Microsoft Dynamics CRM 2011 but I'm sure you can use this method for CRM 2016 and 365 too.
1. Make sure that in the Report Server Configuration Manager there is specified a service account which is a member of PrivReportingGroup and has a _write permissions_ to this group. This account must not be a member of SQLAccessGroup. At least during installation.
2. The setup program also needs a windows service names exactly 'ReportServer$SSRS'. To achieve this, just create a dummy blank new service with a specified name and register it using C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe
3. After that, we need to open Regedit.exe to make changes that will allow the setup program to discover and validate our SSRS instance.
* In [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS] branch add new REG_SZ attribute with name 'MSSQLSERVER' and value 'SSRS'
* In [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SSRS\Setup] branch add new REG_SZ attribute with name 'Version' and value '14.0.600.906' (in my case, you should use your version of SQL server)
4. Now run the setup program (SetupSrsDataConnector.exe). Some next step must show our SSRS instance and we choose it. After all the steps done we will get the last step with important System Checks which all must be green, thanks to our preparation actions.
community.dynamics.com/.../891046
All credit goes to Evgeniy Muzyukov who created this resolution – as figuring this out on your own would be beyond difficult.
This is fairly ‘pro-code’ as involves Creating a Dummy Windows Service and understanding how the CRM Components work with SSRS and ASP.Net – so not an easy one - but we got this working within 2 hours by following these steps and being patient with it.
And then from there, we have the usual SSRS functionality working with Dynamics v8.2, SSRS 2017 and SQL 2019.
The in-place update from SQL 2016 to SQL 2019 for Developer Edition was very smooth and works well with Dynamics v8.2 On-Prem without having to take any steps in Dynamics.
We will be doing the same update on SQL Standard Edition in a weeks time, so will report back on that one, but should be the same in having no negative impacts on Dynamics.
But.. the challenging bit is (as you might expect if you know SQL!) is SQL Reporting Services. (SSRS)
From SQL 2017/2019, SSRS is a separate product from SQL Server Core - and so upgrading to 2019 will uninstall SSRS, so you need to manually install SSRS 2017 after upgrading to SQL 2019.
Now.. SSRS 2017 is not compatible with Dynamics v8 or v9 as the Reporting Extensions Module does not work with it. But (another one!), this can be worked round thanks to some excellent resources and guides online from the community.
I'll put my guide on how to do this in separate post here.
We are planning to test it to see if we can use SQL 2019 with Dynamics 365 v8.2 - as the advantage of SQL 2019 is the ability to enable full Encryption at Rest which is a key feature for some of our remaining On-Prem Clients.
Everything in my experience of Dynamics would lead me to think that using a newer version of SQL would *not* be a problem given how CRM and SQL work together - but will be happy to share our practical results here once we are done if useful?
Hi Allison,
Thanks for reaching community platforms. As of now , we do not see the current software compatibility list documentations for Dynamics 365 CE v8 or v9 indicating such tests.
For now the highest tested version of SQL server compatibility with Dynamics 365 CRM v8 and v9 looks like ::
Dynamics 365 version 8 ::
Microsoft SQL Server 2016, Enterprise/Standard/Developer with Cumulative Update 2 (CU2) Must have updates installed from Update Catalog
support.microsoft.com/.../compatibility-with-microsoft-dynamics-crm-2016
Dynamics 365 CE version 9 ::
Microsoft SQL Server 2017 Enterprise1*
Microsoft SQL Server 2017 Standard1*
Microsoft SQL Server 2017 Developer (for non-production use only)1*
Important ::
1* ::
Requires Microsoft Dynamics 365 Server, v9.0 (on-premises) Update 0.3.
SQL Server Express editions are not supported for use with this version of Dynamics 365 Server.
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/software-requirements-for-microsoft-dynamics-365-server
Please mark this reply as answered if these comments help.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (