topic Re: Performance Issue with .SDE Connection in ArcGIS Pro in ArcGIS Enterprise Questions

Performance Issue with .SDE Connection in ArcGIS Pro

Kristofer — Thu, 22 May 2025 17:29:42 GMT

Hi All,

Hope you all doing well.

We are currently facing a performance issue while working with our PostgreSQL connection file (.sde) in ArcGIS Pro. When we attempt to create or edit layers in the .sde connection, it takes an unusually long time—even creating a single layer.

Postgres is Installed on dedicated VM.

Could you please suggest any potential optimizations or configurations that might help improve the performance.

Thanks & Regards,

Kristofer

Re: Performance Issue with .SDE Connection in ArcGIS Pro

RyanUthoff — Thu, 22 May 2025 17:48:13 GMT

It could be several things that are causing performance issues and it's hard to troubleshoot without knowing your IT architecture.

Are the resources on your postgres VM good? Not maxing out or anything?
Where is ArcGIS Pro in relation to the postgres VM? I'm assuming your end users aren't in the postgres VM itself, so are they all on their own machines? Are they using VPN to connect to the DB? Using VPN to connect to DBs (for example, desktop Pro users requiring VPN to access DBs that are hosted in the cloud) will significantly impact performance.
Can you install ArcGIS Pro on the Postgres VM to see if you can replicate the slowness there? If you cannot replicate the slowness, then it will be a network related issue.
Do you have any web maps (like in ArcGIS Enterprise) that are also using DBs from that Postgres VM? If the answer is yes, do you have any performance issues there? If you do not have any performance issues there, then it is likely a network issue between your end users and the VM.

Re: Performance Issue with .SDE Connection in ArcGIS Pro

DavidPike — Thu, 22 May 2025 19:27:37 GMT

All excellent points from Ryan. I'll just add that if you're using traditional versioning - ensure you're compressing the DB at least weekly.

If there's specific layers which are slow, check the spatial indexes also.