ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
GP 2024 Pre-Upgrade Checklists GP 18.2 to GP 18.6Server Name:Server Name:Server Name:
2
#TasksDEVResourceDateTimeUATResourceDateTimePRODResourceDateTime
3
Official Microsoft Documentation
4
Upgrade Checklist:
5
https://docs.microsoft.com/en-us/dynamics-gp/upgrade/upgrade-checklist
6
Upgrade path: 18.2 >> 18.3 >> 18.4 >> 18.5 >>18.6 (October 2023)
7
https://learn.microsoft.com/en-us/dynamics/s-e/gp/hot_topic_mdgpupgrade_415
8
Product Release download:
9
https://learn.microsoft.com/en-us/dynamics/s-e/gp/mdgp2018_release_download_378?source=recommendations
10
11
Request offline registration keys for UAT (not connected to internet)
12
1Verify Hardware Compliance
13
Request a snapshot of citrix before install
14
2Post all batches (End user's Responibility)
15
3Check if all batches are posted. (End user's Responibility)
16
4Asks all users to exit greatplains (Admin >> Utilities >> User Activity)
17
5Print Critical report
18
 - Trial Balance Summary - (Posting + Inactive) 1/30/24
19
CO100
20
CO200
21
CO999
22
6Backup Databases
23
DYNAMICS
24
CO100 / CO200 / CO999
25
26
7Backup important files
27
Dynamics.set and Dex.ini
28
Reports.dic
29
Mekorma files / signature
30
Smartlist Builder
31
SmartConnect
32
Extender
33
34
35
8Perform Checklinks on CO100 Database (can be done a week before upgrade)
36
Financial Checklinks
37
Sales Checklinks
38
PM Checklinks
39
Inventory Checklinks
40
System Checklinks
41
Company Checklinks
42
Perform Checklinks on CO200 Database
43
Financial Checklinks
44
Sales Checklinks
45
PM Checklinks
46
Inventory Checklinks
47
System Checklinks
48
Company Checklinks
49
9Run Scripts to check if there are invalid Records in PO Tables
50
select PONUMBER, DEX_ROW_ID from POP10110 where PONUMBER not in (select PONUMBER from POP10100)
51
select PONUMBER, DEX_ROW_ID from POP30110 where PONUMBER not in (select PONUMBER from POP30100)
52
10Backup IM.Mdb (make 2 backups) / Smart Connect Maps
53
11Backup Report.dic (make 2 backups)
54
12Backup Forms.Dic (make 2 backups)
55
13Backup DYNAMICS after checklinks
56
14Backup COMPANY A after checklinks
57
16Perform Utilities Reconcile on all accounting records
58
COMPANY A / COMPANY B /COMPANY C
59
60
17Execute the following maintenance routine from the following DB
61
DBCC CHECKDB
62
DBCC CHECKCATALOG
63
DYNAMICS DoneDoneDone
64
COMPANY A / COMPANY B /COMPANY CDoneDoneDone
65
66
18Verify that the master..sysservers table has the correct server name entry in the srvname column, if not you will receive an error "Server Not Named" and will not be able to proceed. Execute the script and verify the results matches your computer name.
67
select @@servernameDoneDoneDone
68
(run through all database)
69
19Execute the following statement against the DYNAMICS database and all company database. This statement will correct any inaccuracies in the sysindexes table for each database. This will verify the row counts reports created on the next step.
70
71
72
73
dbcc updateusage(dbname)
74
20Verify that your company databse and all company databse are owned by DYNSA and/or the DYNSA SQL login exist. Verify That they have the same server collation. Execute this script from master database
75
sp_helpdbDoneDoneDone
76
(run to master database)
77
21Ensure that any custom tables or stored procedures you may have in your databse do not contain spaces in the name. (all database)
78
select name
79
from sysobjects
80
where name like '% %'
81
22Create a dexsql.log before you begin the update process. Change the following statements to TRUE in the Dex.ini
82
SQLLogSQLStmt=TRUE
83
SQLLogODBCMEssages= TRUE
84
SQLLogAllODBCMessages=TRUE
85
23Make sure you have enough disk space for the conversion to be successful .
86
A. Make sure you have enabled the following
87
Recovery model is set to simple (right click databse>>Properties>>Options
88
Tab>>Recovery Model)
89
B. The second check is to execute the following script to identify your largest table by size in megabytes, not row count. It will be the first record in the result set. You will need to look at the 'Total Size KB' column and translate the value that is displayed in 'KB' to megabytes. You do this by taking the value in the Total Size KB column and divide it by 1024. Next, take this result and multiply it by 3. This is the amount of drive space you will need to convert your largest table. So, if your SOP30300 table is 10GB, then you will need to have 10GB of free space in the database file, log file and TempDB.
90
SELECT [total size KB], B.rows, O.name
91
FROM (select sum(convert(decimal(10,0),dpages)*8129/1024)
92
[total size KB], id
93
FROM sysindexes group by id)
94
A INNER JOIN sysindexes B ON A.id = B.id and B.indid in (0,1)
95
INNER JOIN sysobjects O ON B.id = O.id WHERE B.rows <> 0
96
ORDER BY [total size KB] desc
97
24Optional steps Use the following step to shrink the tempdb database
98
99
Database Upgrade Checklists
100
1Make a Final backup of