AnsweredAssumed Answered

Why does it take deleting a version to move some records from the A and D table to the business table

Question asked by kreuzrsk on Nov 30, 2017
Latest reply on Dec 6, 2017 by ahmadabusaleh

We have a versioned SDE 10.2 geodatabase in SQL Server 2012 with users running ArcMap 10.4.1.  There are a dozen versions directly  off the default with no child versions.  Users reconcile, post, reconcile before the database is compressed once a week.  One of the users was looking at the data via the Microsoft SQL Server Management Studio and noticed that records were missing from some of the business tables.   After looking into it I discovered that in some cases there are over 3000 records in a couple of the A tables going back to December of 2016.  

 

I restored a copy of the most recent version of the database to development and went through reconcile / post / compress on all the versions.  a handful of records moved to the business tables but most of those in the A tables remained in the A tables.  Only after deleting all the versions were the remaining records moved from the A tables to the business tables.  After deleting all the versions the record counts are all correct and the A / D tables are now empty.  Anyone ideas on why the versions would have to be deleted for those records to finally move?  Thanks

Outcomes