Microsoft Dynamics CRM (Archived)

Microsoft Dynamics 365(On Premise) with SQL Server 2017

(1) Share

Report

Posted on by ISMAIL TUTUMLUER

399

Is there any update date when can we run Microsoft Dynamics 365(On Premise) with SQL Server 2017 ?

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

Guido Preite 54,086 Moderator on at

Like (0)

Report

A date is not available and Microsoft normally doesn't advice about these kind of requirements.

Keep in mind that the current OnPremise version of Dynamics 365 is the 8.2 and supports SQL Server 2016. As the next OnPremise version will be based on 9.x, we don't know if previous versions will be updated or if 9.x supports SQL Server 2017 or not.

Do you have a specific reason for SQL Server 2017 or is just a licensing issue?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello guys,

I was looking CRM / SQL information because I'm joining a Dynamics projects, and I figure out a question regarding the post blogs.msdn.microsoft.com/.../microsoft-dynamics-365-with-sql-server-2016-cumulative-update-2-cu2 : on one hand they say "Compatibility Level 110 is still mandatory", and on the other hand they're talking about Native Compiled Stored Proc & ColumnStore.. which is AFAIK not compatible. Can you clarify this point ?

So From my side I wonder (and expect) an aligned database compatibility level for SQL 2017.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I am facing the same issue, any update on this ?

Was this reply helpful? Yes No
CRM2013USER 177 on at

Like (1)

Report

I recently installed D365 v9.0 on SQL Server 2017, but Reporting Extensions will not install because it can't find the 2017 Reporting Server instance, which is a separate install in SQL Server 2017. So, I'm guessing it's not supported although I have seen other blog posts saying it is. The Reporting Service instance is definitely installed and running, so I'm not sure why D365 cannot find it.

Was this reply helpful? Yes No
awalters 3,079 on at

Like (0)

Report

I was just thinking about trying this the other day, but saw that separate instance thing and decided to stick with 2016. I did find an official MS requirements page that said 2017 was supported for 9.0, though. Given the other installation issues (which seem to be that there are some older components in the newer install), I wonder if this is related?

Was this reply helpful? Yes No
Tim Mischkin on at

Like (0)

Report

Same issue. Did you find a workaround in the meatime becaus you have mentioned other posts?! Any kind of hint is highly appriciated! Thank you!

Was this reply helpful? Yes No
awalters 3,079 on at

Like (0)

Report

There's a workaround to upgrade an org from v8.2 to v9, but it's unsupported (can find info here - community.dynamics.com/.../300064). I definitely wouldn't suggest doing this on any system you're going to keep.

However, I don't know if anyone's tried this with SQL 2017 - everyone I know has been using 2016. I think the issues may be related, but I'm not sure if the workaround for one will have any effect on the other. Honestly, I doubt it, but...

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

I was able to make it work with SQL Server 2017. But you need to have the Reporting Services on a SQL 2016 instance (named instance on my case). The only problem is the Reporting Services node. There is a filter in the Microsoft application that excludes versions over SQL 2016.

Was this reply helpful? Yes No
Ahmed Ghaib 107 on at

Like (0)

Report

I have the same problem

did you find any solution for that

Was this reply helpful? Yes No
Alexandros Vathis 15 on at

Like (0)

Report

Hi mate, check this conversation, it seems they find a solution..

community.dynamics.com/.../crm-reporting-extension---ssrs-instance-is-blank

Was this reply helpful? Yes No