Latest Contributions by George_Thompson

I would contact technical support about this issue. ... View more

Thanks for that information. This may be a case to work with technical support on a deeper investigation. ... View more

What do the resources on host look like? After the upgrade, is the deployment using more resources (RAM / CPU)? With that delay on the server side, it seems that it is waiting for the server machine to respond. Random question: are the 11.5 machines fully patched? ... View more

As @SimonSchütte_ct mentioned, your EGDB is a "lower" version that your Pro client. It can be upgraded following this documentation: https://pro.arcgis.com/en/pro-app/3.4/help/data/geodatabases/manage-oracle/upgrade-geodatabase-oracle.htm You also would need to connect with the SDE user in order for the upgrade button to "appear". This is common with many organizations that the Pro client is newer than their EGDB. ... View more

In the new architecture, is the PostgreSQL geodatabase in the same location as the new 11.5 machines? Is this in a cloud deployment or local? Not sure I have an answer but curious. ... View more

Are you receiving errors when publishing? How are the resources on the RDBMS and Enterprise when publishing? How often is the data changing? What is the data (point / line / poly)? ... View more

I would log a case with Technical Support to investigate this issue....... ... View more

I have a few questions: Are you still planning on using ArcGIS Pro for editing the data if you move to PostgreSQL? Do you have multiple editors of the data at the same time? Are you publishing out the data to services of any kind? Is ArcGIS Enterprise (or Server) used at all? Generically, you will lose the true functionality of the geodatabase if you move to PostgreSQL. This means that things you list above, plus other advanced geodatabase functions like topology / networks / feature datasets / / etc. There are also some limitations if the data is in a database (with / without spatial type): https://pro.arcgis.com/en/pro-app/latest/help/data/databases/databases-and-arcgis.htm Editing: https://pro.arcgis.com/en/pro-app/latest/help/data/databases/databases-and-arcgis.htm#ESRI_SECTION1_A188C2B1C8C54C7DA3233892FC742552 Hope this helps! ... View more

Not an expert in this area, but I have seen people who automate do it in batches (of like 500 - 1000), which cuts down on the potential impact of a "limit". This is mainly using Python or something like that. ... View more

There may be a timeout on the service side causing the error after a certain period. I have also seen machine resources cause issues when exporting data from a service. Do you own the WFS service? ... View more

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-server/ta-p/1181710   ... View more

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-sqlserver.htm 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-d-000008079 before connecting to the EGDB in Pro. ... View more

Here is the documentation to support this: https://enterprise.arcgis.com/en/system-requirements/11.5/windows/database-requirements-sqlserver.htm ... View more

I would recommend reaching out to technical support to investigate if it is related to the release last night. ... View more