Adding time estimates to Upgrade

[MichaelBartlett]

I recently upgraded from 2024.1.1 to 2025.0.1.

It would not connect to the database.  After several retries I found out the upgrade was updating some Integer to BIGINT datatypes.  I understand it may be hard to estimate the actual time, but it seems like you could check the count of records it was going to update and at least display a message if it is anticipated to take a long time.

Also I found no mention of this in the installation instructions, just a heads up would be nice or some indication it was actually doing something.

[ChrisTaylor2]

I JUST got past this exact issue this afternoon with the help of Support after over a week of troubleshooting. I couldn't figure out why my 2025.0.1 upgrade wasn't completing successfully after trying it several times. It turns out that the database portion of the upgrade took 1h 45m to complete! I didn't even know that was part of the process and had just been expecting it to be ready once the Server install was done, then assumed there was some other issue with the install when I hit the 'Configure Database' screen.

[JamesBrattonVHB]

I had a similar experience.  ArcGIS Monitor install said it was done, but Monitor said it could not connect to the database.  I checked again several times.  Over 24 hours later, it started working.  I found out that it was still upgrading after Esri Support asked me to check the database.  The following query returned 2 rows instead of 12.

SELECT id, name from agm_schema where name LIKE '%2025%';

[Timothy]

We applied the INT to BIGINT fields fix in 2024 under the direction from esri support. I wonder if the upgrade process will handle this appropriately or not. Waiting for 2025.1 before upgrading.