We are moving off of SQL Server 2016 to SQL Server 2022. These are two different servers.
My plan is do database backups from SQL Server 2016 and restore them on SQL Server 2022. Then in some cases upgrade the geodatabase to 11.5 and others we will leave it at 10.9 until the calling applications can be updated. We will also check for permission issues as that always seems to be an issue. The databases have a combination of traditional versioned and non-versioned data.
Is there additional things that will need to be done to the restored databases to make them work properly?
So far in my testing, I've only seen an issue with GDB_items not being updated to the 11.5 fully qualified name. All the documentation I can find doesn't seem to list any additional steps after the restore.
Any recent insight would be appreciated.
Take a look at the notes here before you run the upgrade: https://pro.arcgis.com/en/pro-app/3.5/help/data/geodatabases/manage-sql-server/upgrade-geodatabase-s...
Also, after the restore, you need to make sure that you re-sync any database logins (SDE, DATA, GIS, etc.): https://support.esri.com/en-us/knowledge-base/re-synch-sql-server-logins-or-users-after-restoring-a-...
before connecting to the EGDB in Pro.
I have done those things. Just looking for additional steps may need to be done.
The other thing would be to repoint your services to the new SQL Server instance.
Here is some information and process to investigate: https://community.esri.com/t5/arcgis-enterprise-documents/update-arcgis-server-services-after-sql-se...
Hi JeriSue. I’m not sure what you mean by “an issue with GDB_ITEMS not being updated to the 11.5 fully qualified name.”
Beginning with Enterprise 11.x / ArcGIS Pro 3.x, we removed the database name field from all SDE/GDB enterprise geodatabase repository tables. This change was made specifically to support renaming SQL Server databases that host enterprise geodatabases.