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; } } }

Read EGDB Feature Class After Publishing Versioned Feature Service

teofilosalgado

Hello all!

I have a question regarding accessing data in an Enterprise Geodatabase in a branch-versioned Feature Service scenario:

Using ArcGIS Pro, can I read branch-versioned feature classes directly from my Enterprise Geodatabase (SDE connection) after I published a branch-versioned Feature Service? Will it point to the “sde.DEFAULT” version?

I would like to perform some heavy geoprocessing tasks, and my Feature Service performance isn’t keeping up. My Enterprise Geodatabase, on the other hand, is robust and more than capable of handling my tasks.

Thanks.

Encuentra más publicaciones etiquetadas con

Geodatabase

Desktop

Feature Services

Accepted answers

RussellBrennan

Thanks for the examples, it might be worthwhile looking into taking the data offline in Pro to perform these types of analysis. With the data offline we can potentially query larger volumes of data faster for this type of analysis. You can then make edits to this data if needed and sync the changes back through the feature service.

Yes you should be able to run some subset of tools which will operate only on the default version using an SDE connection file, Append will work but I am not certain about others.

All comments

joyoung_kerrvilletx

The read only connection should be pointing to sde.DEFAULT. That is how it works on my read only connections and the Versioning tools in ArcGIS Pro are greyed out.

You mention geoprocessing tasks. If the branch versioned data is being used as read only input in the tasks, then you should be able to use the Enterprise Geodatabase connection without issue. Only editing requires you to go through the feature service.

RussellBrennan

You can only connect to the default version from ArcGIS Pro. Some geoprocessing tools such as Append should work but others may not. I am not sure there is a comprehensive list of which will and will not work. Can you describe some of the tasks. I may be able to provide some pointers to assist with performance.

teofilosalgado

Sure! Most of my tasks consist of large spatial and attribute joins. For example, one common task is to spatially join a large point Shapefile (100,000 features) against my Utility Network Device Layer (around 20 million features). We also consolidate a lot of information by summarizing Utility Network Layers based on their attributes.

To clarify: if I understood correctly, in addition to reading from a branch-versioned Enterprise Geodatabases via an SDE connection, can I also use tools like Append to write data back into the DEFAULT version of a branch-versioned Enterprise Geodatabase?

teofilosalgado

Thanks for the answer! The performance impact of reading an entire Device layer through a Feature Service was significant; I'll be moving my geoprocessing tasks to SDE connections ASAP.

RussellBrennan

Yes you should be able to run some subset of tools which will operate only on the default version using an SDE connection file, Append will work but I am not certain about others.

RussellBrennan

For heavy analysis happening client side in Pro there is a significant cost to pulling all of the data on the client. We are investing a lot of effort in trying to make this faster from multiple angles.

I would push you to look into offline workflows. We recently did some work to better support downloading large datasets: https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/introduction-into-offline-map-areas-prepared-ahead-of-time This might be a good option for your workflows.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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