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,

MG.-
Mariano Gomez, MVP

Comments

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?
Thanks,
Scott
March 11, 2020 at 4:19 PM
Mariano Gomez said…
Scott,

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.
March 16, 2020 at 10:14 PM
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.

Thanks,
Jason
May 5, 2020 at 1:49 AM
Mariano Gomez said…
Jason,
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:

https://experience.dynamics.com/ideas/idea/?ideaid=2388371a-18a4-ea11-8b71-0003ff68c1c1
June 1, 2020 at 10:58 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more