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

Check if Enterprise Geodatabase is reconcilied in ArcPy

AlbertoLópez

Hi;

In a python/arcpy script I have to do a compress database and a regenerate index. I don't have to do a reconcilied version.

But previously I have to validate if users have reconcilied the data in the default version of the enterprise database.

Is there any way to do this with ArcPy?. Maybe doing a query to the sde.version table or other table. But I do not how.

Thanks. Greetings.

Najděte více příspěvků označených jako

Accepted answers

All comments

DanPatterson_Retired

do you mean arcpy specific functions or workflows?

Using Python scripting to batch reconcile and post traditional versions—Geodatabases | ArcGIS Desktop

AlbertoLópez

Hello Dan;

Thanks.

I mean specific arcpy functions, I think.

But I had already read the link. But in it, there are no code to check if the database is consolidated and my script code can not do the reconcile because there are conflict that the user has to resolve (not the python script).

I need to do a compres an regenerate index database only if the users have consolidated the data in the enterprise database.

Regards.

DanPatterson_Retired

Alberto López‌ I didn't find anything specific and I kept coming back to tools in Arctoolbox. So if there is a way to do it through a workflow in arctoolbox, then that can be scripted by calling those tools piecewise. Your best luck is to have someone that has done your workflow before, jump on board.

JoshuaBixby

Sharing with Geodatabase‌

I must admit I am not quite following both what you are trying to do and what issue you seem to be having. You use the term "consolidate", but that isn't a geodatabase term. Can you elaborate on what you mean by "users have consolidated data in the enterprise geodatabase"?

Are you looking to do a full compress of the enterprise geodatabase? Even if an enterprise geodatabase cannot be fully compressed, there are advantages to doing partial compresses, so why not just compress the database whether all the users have reconciled and posted their data or not?

AlbertoLópez

Thanks Dan;

I will try to do a query in the "sde.version" table like this:

if status field contains 3355443X maybe the database is consolidated

if status field does not contains 3355443X maybe the database is not consolidated

Arcsde 10 - versions table, status 33554433

AlbertoLópez

Thanks Joshua;

When I said "consolidated" I mean that if the users have reconciled and posted their data in the default version of the geodatabase?.

I need to compress all geodatabase.

I can not compress the geodatabase if all users have not reconciled and posted their data in the default version of the geodatabase, because there are an esri recommendation about it:

"To maintain good performance in a geodatabase containing versions, there are a few key administrative tasks that should be run regularly. A recommended workflow for administrators is to frequently reconcile and post, compress the geodatabase, then run the Analyze Datasets and Rebuild Indexes geoprocessing tools. This sort of routine maintenance can be set up to run nightly as a script or by building a model."

I understand that it is better reconciled and posted before that do the database compress, etc

Regards.

JoeBorgione

Take a look at: Using Python scripting to batch reconcile and post versions—ArcGIS Help | ArcGIS Desktop

We have used this approach for some time; seems like I modified ESRI's approach such that once the versions are reconciled and posted I delete them and recreate them at the end. Sorry, since I recently switched jobs I don't have access to the actual code I wrote anymore.

JoshuaBixby

The Geodatabase compression—Help | ArcGIS Desktop states:

It may not always be possible to reconcile, post, delete versions, and disconnect all users before compressing. For instance, if you are tracking history using versions or need to maintain design versions for a project, the historic and design versions hold a state within the state tree; therefore, these states are not removed during compression of the geodatabase. You can successfully compress without doing all these steps, and you will still see performance improvements.

Don't let the "best workflow" get in the way of a "good workflow." Ideally, a geodatabase would be compressed to State 0 every time, but that can be a huge undertaking when an enterprise geodatabase has even a modest number of users. If regular, partial compressions aren't doing enough; you can always reconcile and post all the versions as the geodatabase administrator, but you would need to make assumptions about how to handle conflicts.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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