Microsoft Dynamics GP Database Installation and Upgrade Statuses

I have to admit that to deliver this post I had to dig deep into the bowels of the Microsoft Dynamics GP Utilities. Installation and upgrade statuses don't seem to be anywhere (that I could find anyways) handy and can be very important when looking at a DEXSQL.LOG file for reasons of a failure during any of these processes.

Status ConstantStorage Value
DU_STATUS_DONE
0
DU_STATUS_START
1
DU_STATUS_INSTALL
2
DU_STATUS_UPGRADE
3
DU_STATUS_BIND_DEFAULTS  
7
DU_STATUS_RECOMPILE
8
DU_STATUS_CONVERT
23
DU_STATUS_POST_CONVERT
30

During the installation or upgrade of a database, status codes are recorded in the DYNAMICS..DB_Upgrade table for each Microsoft Dynamics GP dictionary being updated.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

DavidMO said…
I noticed other values while trying to track the progress of our 25 company update using this script I built, below. I was thinking of building in a case statement with the various status.
48, 53, 54, plus some others that flash by pretty fast. Any ideas what the complete list includes?


SELECT db_name, PRODID, db_verMajor, db_verBuild, db_status,
Left(Convert(varchar(11) ,start_time, 0),11)+' ' + right(Convert(varchar ,start_time, 8), 8) as StartTime,
Left(Convert(varchar(11) ,stop_time, 0),11)+' ' + right(Convert(varchar ,stop_time, 8), 8) as StopTime,
Convert(varchar, stop_time - start_time, 8) AS Duration,
Case
When db_status = 0 then '1 - Upgraded'
When db_status <> 0 Then '2 - IN PROCESS'
End as Status
FROM DB_Upgrade WHERE PRODID = 0 and db_verBuild = 1860
Union All
SELECT db_name, PRODID, db_verMajor, db_verBuild, db_status,
'' as StartTime, '' as StopTime,
'' AS Duration,
'3 - Not Upgraded' as status
FROM DB_Upgrade WHERE PRODID = 0 and db_verBuild < 1860
ORDER BY status, StartTime asc
January 1, 2012 at 12:32 PM
DavidMO said…
Here are the Values I pulled from a Trace ran while performing the 12/21/2011 GP2010 End-of-year upgrade
set [db_status]=0
set [db_status]=1
set [db_status]=6
set [db_status]=7
set [db_status]=8
set [db_status]=9
set [db_status]=10
set [db_status]=11
set [db_status]=12
set [db_status]=13
set [db_status]=14
set [db_status]=15
set [db_status]=16
set [db_status]=17
set [db_status]=23
set [db_status]=30
set [db_status]=47
set [db_status]=48
set [db_status]=49
set [db_status]=50
set [db_status]=51
set [db_status]=52
set [db_status]=53
set [db_status]=54
set [db_status]=55
set [db_status]=56
set [db_status]=59
January 3, 2012 at 1:06 PM
Mariano Gomez said…
Dave,
Thanks for the additional input! This is a great compilation.

MG.-
January 5, 2012 at 9:20 AM
jpkd said…
Here's a link to a script I wrote a while back to see the progress of an upgrade. It's only really useful when there is more than one company database. It doesn't really take into account the db_status column as a description of what is currently happening as much as using it for noting which DB is currently being upgraded. The script gives a fairly good idea of how long the process will take after the first database has been completed. So far it's been pretty accurate.

Upgrade progress script
July 28, 2012 at 3:46 PM
Dbruni5 said…
Thanks for posting, this enabled me to restart the upgrade of my old company after a reinstall of the database to a new machine.
August 7, 2015 at 4:41 PM
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