Manage Geodatabase Functionality Failing to Load in Timely Manner

Question

I am currently using ArcGIS Pro 3.1.1 and trying to apply Global IDs, Editor Tracking, and Versioning to a dataset within our SDE.  After I disconnect users, I right-click on the dataset I need to apply these settings to and click Manage.  Once the dialog box pops up, the Manage geodatabase functionality window takes several minutes to load.  By the time the options finally appear, users accessing the SDE from the field have automatically connected and I can't apply the changes.

I was able to do all of these changes within a couple of minutes in ArcCatalog, so I am not sure why ArcGIS Pro's Catalog is struggling with database management.  Can anyone offer any tips on how I can access these management features without it taking ages?

JasminePrater · Answer

Yes, everything is in the same building.  I will reach out to support to see if they can assist if it doesn't get better after the upgrade.  We will be moving to SQL Server 2019 when we do the upgrade, if that helps.

I did everything in ArcCatalog, as I recently started using ArcGIS Pro and have been using ArcMap for years.  It still works fine in ArcCatalog, but I'm trying force myself to do everything in Pro to make sure I'm prepared for our transition to Enterprise 11.  If I'm in a time crunch, I will do it in ArcCatalog, but I want to stop using it as a familiar crutch.  If support is able to offer insight and/or assistance, I will update this thread.  I appreciate your help!

George_Thompson · Answer

I have not heard of that yet. Is the SQL Server instance in the same location (i.e. building) as the Pro clients?

It may be good to work with technical support on this as they can dive in deeper.

I will say that SQL 2016 is at the end of the supported list for Pro 3.1 (https://enterprise.arcgis.com/en/system-requirements/latest/windows/database-requirements-sqlserver.htm) but should still work.

I wonder if the upgrade would help the interaction.

What was the previous version of Pro that seemed to work fine?

JasminePrater · Answer

We don't have a DBA for GIS, that's me now.  😅

We are running SQL Server 2016.