nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Azure ArcGIS to on-prem database

asinha_ppc

ArcGIS Enterprise 10.9.1 has been migrated to Azure.
Oracle 19.3 SDE feature Classes are on-prem.

Connecting, viewing and exporting databases is extremely slow with this configuration. Something that was taking a minute with on-prem ArcGIS Pro is now taking 20+ mins. While we were expecting some performance degradation, this seems excessive.

Our IT is not planning on moving Oracle to Azure in the near future. Any suggestions?

Thanks!

Vind meer berichten getagd met

Accepted answers

MMBR

Unfortunately, there is no alternative for this problem. ArcGIS Enterprise Portal & Server must be on the same LAN Local Area Network of the Enterprise Geodatabases to have appropriate performance. Either keep the entire deployment on premises or move the entire stack to the cloud. The connection to databases requires high network bandwidth and low network latency, if you have the ArcGIS Enterprise in the Cloud and the Database on premises, or vice-versa, you have low bandwidth and high latency, therefore performance is expected to be very poor. This is very well-known.

All comments

MichaelJenkins

Good point and an important one to mention. It really is 'all or nothing'.

DevinBartley2

Incase anyone is wondering, the inverse applies - you will experience similar problems if you try to use an on-prem ArcGIS Pro install connecting to a database in the cloud. The solution in the case that your ArcGIS Enterprise and database have been moved into the cloud is to put a ArcGIS Pro remote desktop in the same azure region as the database and enterprise install and connect from your local computer to that desktop for your ArcGIS Pro work. There are various GPU enabled options for this, some of which utilize partial GPU's and cost less.

MMBR

If using ArcGIS Pro Branch Versioning, then have the Entire Deployment on Premises or in the Cloud, avoid keeping Portal separate as suggested above. I understand that it might be possible to keep Portal in the Cloud and have Server + Databases on Premises, but this is still not ideal once Portal needs to be federated with Server, it not just about HTTPS traffic, there is other communication between Portal and Server behind the scenes, and the fact that in this scenario the HTTPS traffic between Portal and Server will have to cross at least 2 different firewalls. Hence, the recommendation that I always make to my customers is to have the entire stack deployed on Premises or in the Cloud to avoid other unexpected performance issues.

MichaelJenkins

Your IT department made a bad decision. If this is what you are stuck with, you might be able to have an on-prem ArcGIS Server that connects to Oracle and is federated to your Azure hosted Portal. That way the server and DB are close to each other and everything between server and Portal/clients is just web traffic. Or set up a DB in Azure and replicate data from on-prem to Azure on a schedule.

MMBR

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.