Monday, February 26, 2018

Microsoft Dynamics GP: Running System and Company Databases on Azure SQL - Part 3

In Part 2 of this series, I showed the data migration process for the Microsoft Dynamics GP system database. I also provided a few reasons why the Azure SQL platform is not supported. This vlog article will skim through the migration process for the company database and will examine more reasons why Azure SQL is not a supported configuration.

In this video I also examine other topics like the Azure SQL Query Editor which is currently in preview mode, and vertical elastic queries.

Until next post,

Mariano Gomez, MVP


Unknown said...

Hi Mariano, in these videos you actually prove that it does NOT work. Several objects are not migrated and you cannot login. Am I missing something here and or has anything changed since you posted these videos such that GP actually works against Azure SQL managed instance?

Mariano Gomez said...


The final conclusion is, "somethings do work, but not EVERYTHING". To your point, it does NOT work, but when I set out to do this video, I wanted to take a pragmatic approach and simply walk through to arrive at that conclusion. The idea was to do all in my power to make it work, only to conclude not everything does and therefore this is not a supported configuration.

Hope this helps.

Unknown said...

Hi Mariano,

Has anything changed with SQL Managed Instance that would resolve the issues encountered in 2018? I saw a recent video on enabling CLR assemblies in managed instance which would fix the workflow and doc attach issues encountered. I would think that Microsoft was working towards "Managed Instance" as a true cloud deployment that can function EXACTLY like an on-premise install.


Mariano Gomez said...

One of the nuances of working with SQL CLR is that any assembly loaded into both the GAC and SQL Server must be the exact same version (i.e. down to the patch level, not just Major.Minor.*).

Not to mention, the Utilities still need work.

I can only speculate the GP dev team has not done anything remotely close to a compatibility test with SQL Server Managed Instance as this would have probably already made it to the System Requirements page.

Please vote for my idea/suggestion: