Record a video of your upgrades so the issue can be captured
run the SQL profiler during upgrades to collect evidence (track starting and completed)
run the task manager and monitor CPU and memory (sorted by memory usage descending)
WORKAROUND:
Per Ramil via skype on 11/27/2023 4:40pm "stop dbmc and then run it again without restoring the backup" ... kill the process using windows task manager... "if the cancel button does not respond or not work".
ADDITIONAL NOTES:
I ran the DBMC 22.3 (8083) upgrade and it says "upgrade...is successful" but the screen froze and that point and I will have to kill it to exit the program. That fact that it froze after the upgrade completed this time indicates the issue may not be with the upgrade programming but with the user interface.
Ongoing issue that needs to be tracked and fixed. Reported by multiple partners and previous staff members over many different versions.
Comments per ray mac:
"it happens when you leave the upgrade tool running without any other activities in the machine. workaround I did there is to make sure there is any mouse movement at least every 5-10mins. that upgrade should be quick though if not freezing."
Comments per Ramil:
There are a lot of factors to consider when upgrading databases and the possible reasons why it is not proceeding smoothly.
Database size. The bigger the db the more memory is required on the computer to cache the running scripts, etc.
Customizations made to the db. Partners need to make sure their changes does not impact the upgrade. Based on experience, some customization have triggers in SQL that breaks the upgrade.
Upgrade path. The bigger the gap, the more scripts to run and the longer it takes to complete it. Example is from v19 to v22.
Possible workarounds:
Multiple database upgrade steps (upgrade the database one major version at a time)
Free up as much RAM as possible on the server
Review database customizations in advance of the upgrade
Reduce the size of the database
Ticket 146187 under MNC. Upgrade log shows this:
[6/14/2023 2:37:49 PM] 155 of 272 scripts. Adding new data to 'AccountingPreference'......
[6/14/2023 2:37:49 PM] 156 of 272 scripts. Adding new data to 'CuteChat4_SupportMessage'......
[6/14/2023 2:37:49 PM] 157 of 272 scripts. Adding new data to 'CuteChat4_SupportSession'......
[6/14/2023 2:37:49 PM] 158 of 272 scripts. Adding new data to 'SystemPlugin'......
[6/14/2023 2:37:49 PM] 159 of 272 scripts. Adding new data to 'SystemUserRole'......
[6/14/2023 2:37:49 PM] 160 of 272 scripts. Adding new data to 'CuteChat4_User'......
[6/14/2023 2:37:50 PM] 161 of 272 scripts. Adding new data to 'SystemPluginAssembly'......
[6/14/2023 2:38:08 PM] 162 of 272 scripts. Adding new data to 'EcommerceTopic'......
DBMC screen shows:
Had to KILL the DBMC and after trying to restore the database backup to try and start over, I got:
Restore of database ... failed...The operation cannot be performed on a database with database snapshots or active DBCC replicas. (Microsoft.SqlServer.SmoExtended)
This is because the upgrade process had created a database snapshot which did not get removed due to the killing of the DBMC.
davidonelson
commented
9 months ago
RECOMMENDATIONS:
WORKAROUND: Per Ramil via skype on 11/27/2023 4:40pm "stop dbmc and then run it again without restoring the backup" ... kill the process using windows task manager... "if the cancel button does not respond or not work".
ADDITIONAL NOTES: I ran the DBMC 22.3 (8083) upgrade and it says "upgrade...is successful" but the screen froze and that point and I will have to kill it to exit the program. That fact that it froze after the upgrade completed this time indicates the issue may not be with the upgrade programming but with the user interface.
Ongoing issue that needs to be tracked and fixed. Reported by multiple partners and previous staff members over many different versions.
Comments per ray mac: "it happens when you leave the upgrade tool running without any other activities in the machine. workaround I did there is to make sure there is any mouse movement at least every 5-10mins. that upgrade should be quick though if not freezing."
Comments per Ramil: There are a lot of factors to consider when upgrading databases and the possible reasons why it is not proceeding smoothly.
Possible workarounds:
Ticket 146187 under MNC. Upgrade log shows this: [6/14/2023 2:37:49 PM] 155 of 272 scripts. Adding new data to 'AccountingPreference'...... [6/14/2023 2:37:49 PM] 156 of 272 scripts. Adding new data to 'CuteChat4_SupportMessage'...... [6/14/2023 2:37:49 PM] 157 of 272 scripts. Adding new data to 'CuteChat4_SupportSession'...... [6/14/2023 2:37:49 PM] 158 of 272 scripts. Adding new data to 'SystemPlugin'...... [6/14/2023 2:37:49 PM] 159 of 272 scripts. Adding new data to 'SystemUserRole'...... [6/14/2023 2:37:49 PM] 160 of 272 scripts. Adding new data to 'CuteChat4_User'...... [6/14/2023 2:37:50 PM] 161 of 272 scripts. Adding new data to 'SystemPluginAssembly'...... [6/14/2023 2:38:08 PM] 162 of 272 scripts. Adding new data to 'EcommerceTopic'......
DBMC screen shows:
Had to KILL the DBMC and after trying to restore the database backup to try and start over, I got: