(again): A tool to transfer the Add\Delete tables to the business table,I???m wondering if there is simple tool that can transfer the Add\Delete tables to the business table. I got the attached model tool but it appears not to do the job[ATTACH=CONFIG]31580[/ATTACH], [ATTACH=CONFIG]31581[/ATTACH]What other tools might transfer the Add\Delete tables to the business tableThank youBestJamal
Not sure why the “rebuild indexes” fails in ArcGIS Pro
What could be the issue here?
Many thanks Timothy for the efforts.
Best
Jamal
Images from the original question
From the screen shots I can see that you are running the Model from the ArcMap interface.1) Did you save the edits and stop editing?2) Try to close the ArcMap after editing and then run the Model from ArcCatalog. Does this help?You must understand that just running the compress will not push all records from the delta tables to the Base table. There should be no one editing the data, when you are attempting the compress if you want a "full compress".
SELECT * FROM DBO.VERSIONS;
Are there other connections to the geodatabase besides the one from which you're attempting compress? Client connections can create state locks and therefore prevent records from A & D tables getting written to base. When you run compress, please ensure there are no other connections.
That process is carried out by the Compress operation, step 2 in your ModelBuilder model. If the Compress failed to do that, than there are still versions or replicas (which as William correctly stated are also technically versions) that haven't been reconciled & posted properly.
Now, being the updates are reflected in the sde.default and its versions by the �??reconcile version�?� tool, the �??communities�?� in the SQL server doesn�??t match the one on the ArcGISNumber of records of the �??communities�?� in the SQL is 781Number of records of the �??communities�?� in the ArcGIS is 788...Which tools can be used to have Number of records of the �??communities�?� in the SQL and in ArcGIS equal?
select * from Communities_Points.DBO.versions
The Compress GP tool you show in your model is responsible for moving rows from the A and D tables into the base table, assuming that no child versions reference the state IDs of those particular rows. Reconciling and posting beforehand (which you've correctly delineated in your model) is what moves your state ID pointers in the geodatabase. That is why reconciling, posting, and compressing are such critical parts of the geodatabase maintenance process.
Do the tools depicted in the screenshot below can transfer the values stored in the Add\Delete tables to the business table?
Jamal,Just a quick observation, but based on your first screenshot in the last post, it shows the dataset being a "replica" ("Is Replica" is TRUE).Are you actually looking in the right database, and compressing the right one? Shouldn't you be synchronizing with the parent and compress there?Other thing: did you actually select "Reconcile and Post with parent version" in the Synchronize Changes wizard? If not, the data will not have been automatically reconciled and posted to your DEFAULT, and you will have to manually reconcile and post the replica version against DEFAULT and subsequently compress.Please also note that even if you don't create additional versions, replication still requires the parent database to be versioned, and a Replica Version will be created upon creating the replica. This is why you need to reconcile and post this replica in the parent database against DEFAULT, and compress, before the edits will show up in the base table.
What might be the issue? Which tool is supposed to be used to get the data updated in the business table?
Jamal, What do you mean with "attached model"? I only see a table... you probably mean you have made some edits in a replica or version, and now wish to transfer these to your main geodatabase and add them to DEFAULT and possibly compress to state 0?Other than using the ESRI supplied tools (synchronize replicas, reconciling & posting version changes, and compress your geodatabase), it is unwise to start messing with the tables in SQL Server Management Studio. You may wreck your geodatabase.If you need to see the state of DEFAULT, including all the Adds and Deletes in an application other than ArcGIS / non-ESRI software (e.g. in SQL Server Managament Studio), you can connect to the Versioned View instead of the base table. It should show you the latest state of DEFAULT including all changes in the Adds and Deletes tables (at least as far as reconciled and posted to DEFAULT, if you don't reconcile and post to DEFAULT, the changes of course won't be visible in DEFAULT).
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.